Security in Practice: Stack, Prompts and Use Cases
An attack where hostile input hijacks the LLM's instructions, causing it to leak data or misbehave. This guide pulls together everything on Onexial tagged security — 10 connected nodes across definitions, workflows, tool stacks, comparisons, prompts and applied use cases — and orders it the way you would actually learn it: vocabulary first, then process, then tooling, then execution. Every item below links to a full node with its own examples and connections, so you can go as deep as you need without losing the map.
Core concepts behind Security
Before wiring anything together, the vocabulary has to be precise. These 4 definitions cover the terms that show up in almost every Security discussion — each one links to a full entry with an example and its own connections inside the graph.
Prompt Injection
An attack where hostile input hijacks the LLM's instructions, causing it to leak data or misbehave.
Jailbreak
A prompt crafted to bypass a model's safety alignment.
MCP Transport (stdio vs Streamable HTTP)
MCP runs either as a local stdio process or as a remote streamable HTTP endpoint — the choice decides auth, deployment and who can reach it.
AI Security
AI security protects systems where the model is an untrusted decision-maker acting on untrusted input with real tool access.
Workflows: how Security runs end to end
Concepts only matter once they become a repeatable process. Below are 3 documented workflows that apply Security to a concrete problem, with the steps, the tools involved and the variations worth testing.
Connect MCP to Internal Systems Without Losing Control
Give agents real access to your CRM, database and docs with least privilege.
Audit MCP Tool Security
A checklist that catches the failure modes unique to model-driven tool calls.
Harden an AI System Against Injection and Misuse
Architectural controls that survive a manipulated model.
The Security tool stack
A stack is a set of tools chosen for one job, not a list of favourites. These 1 stacks show which combinations hold up in production for Security, and what each layer is actually responsible for.
Prompts you can reuse
Prompts are reusable components. Each of these 2 prompts is written to be dropped into a Security workflow with minimal editing, including the context it expects and an example output.
Autonomy Boundary Prompt
Defines exactly what an agent may do alone, with approval, or never.
AI System Threat Model Prompt
Produces a concrete threat model for an AI system with tool access.