Phase 4 settlement. Read the current status of a mandate: pending / operator-approved / operator-denied / executed / expired / cancelled. GATED by AEGIS_GRID_P4_SETTLEMENT_ENABLED.
Part of the AiEGIS server.
Free to start. No card required.
AI agents call grid_get_mandate_status to retrieve information from AiEGIS without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though grid_get_mandate_status only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"grid_get_mandate_status": {}
}
}See the full AiEGIS policy for all 18 tools.
These attack patterns abuse exactly the kind of access grid_get_mandate_status gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Phase 4 settlement. Read the current status of a mandate: pending / operator-approved / operator-denied / executed / expired / cancelled. GATED by AEGIS_GRID_P4_SETTLEMENT_ENABLED.. It is categorised as a Read tool in the AiEGIS MCP Server, which means it retrieves data without modifying state.
Register the AiEGIS MCP server in PolicyLayer and add a rule for grid_get_mandate_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 AiEGIS. Nothing to install.
grid_get_mandate_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 grid_get_mandate_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 grid_get_mandate_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.
grid_get_mandate_status is provided by the AiEGIS MCP server (AiEGIS-ie/Grid). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 18 AiEGIS tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.