Run AGT poisoning, MCP, and prompt-defense checks against arbitrary text.
AI agents invoke agt_policy_check_text to trigger actions in Agentos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
The tool actively runs security analysis checks (poisoning detection, prompt-defense) against arbitrary text input. This constitutes execution of analysis/scanning operations rather than passive data retrieval. While it doesn't modify data, it triggers external processing pipelines. Misuse could involve feeding adversarial text to probe or bypass security checks, making severity medium.
From the tool's definition 'Run AGT poisoning, MCP, and prompt-defense checks against arbitrary text'
Documented attack patterns abuse exactly the kind of access agt_policy_check_text gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentos, and nothing reaches the server without passing your rules. This is the rule we recommend for agt_policy_check_text:
{
"version": "1",
"default": "deny",
"tools": {
"agt_policy_check_text": {
"limits": [
{
"counter": "agt_policy_check_text_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} agt_policy_check_text stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run AGT poisoning, MCP, and prompt-defense checks against arbitrary text. It is categorised as a Execute tool in the Agentos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agentos MCP server in PolicyLayer and add a rule for agt_policy_check_text: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agentos. Nothing to install.
agt_policy_check_text is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the agt_policy_check_text rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for agt_policy_check_text. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
agt_policy_check_text is provided by the Agentos MCP server (@microsoft/agentos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agentos, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Agentos tools catalogued and risk-classified — across an index of 43,000+ MCP servers.