Return the active AGT Antigravity policy runtime status and summary.
AI agents call agt_policy_status to retrieve information from Agentos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves the current status of a policy runtime. It reads data without causing side effects, state changes, or triggering external operations. The verb 'return' and 'status/summary' indicate passive information retrieval characteristic of Read category tools. No arguments are mentioned that could alter system behavior or execute arbitrary operations.
From the tool's definition Tool description states 'Return the active AGT Antigravity policy runtime status and summary' — a purely informational retrieval operation with no modification, deletion, or execution capability.
Documented attack patterns abuse exactly the kind of access agt_policy_status 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_status:
{
"version": "1",
"default": "deny",
"tools": {
"agt_policy_status": {}
}
} agt_policy_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return the active AGT Antigravity policy runtime status and summary. It is categorised as a Read tool in the Agentos MCP Server, which means it retrieves data without modifying state.
Register the Agentos MCP server in PolicyLayer and add a rule for agt_policy_status: 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_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agt_policy_status 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_status. 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_status 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.