> For the complete documentation index, see [llms.txt](https://ai-security-docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-security-docs.akto.io/agentic-guardrails/concepts/threat-policy.md).

# Guardrail Policy

Guardrail policies are customizable filters that monitor and analyze your agent traffic in real-time to detect and mitigate agentic security threats. These policies protect your AI agents and MCP endpoints by identifying and blocking malicious activities, such as prompt injections, tool abuse, and attacks outlined in the OWASP Core Rule Set including Cross-Site Scripting (XSS) and SQL Injection. You can configure policies to enforce geofencing, block traffic based on IP CIDR ranges, and control tool access patterns.

To create guardrail policies, head to [Create Guardrail Policies](/agentic-guardrails/how-to/create-guardrail-policies.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ai-security-docs.akto.io/agentic-guardrails/concepts/threat-policy.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.