Report the calling account's plan, key usage, and limits. Use this to introspect what the caller is allowed to do. Agents that hit rate limits or key-count caps can call this to explain the limit to the human and suggest upgrading if needed. Args: api_key: GeodesicAI API key (starts with gai_) Re...
Risk signalsHandles credentials or secrets (api_key)
Part of the Governance Platform server.
Free to start. No card required.
AI agents call account_status to retrieve information from Governance Platform 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 account_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": {
"account_status": {}
}
}See the full Governance Platform policy for all 31 tools.
These attack patterns abuse exactly the kind of access account_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.
Report the calling account's plan, key usage, and limits. Use this to introspect what the caller is allowed to do. Agents that hit rate limits or key-count caps can call this to explain the limit to the human and suggest upgrading if needed. Args: api_key: GeodesicAI API key (starts with gai_) Returns: plan: The user's current plan — one of pilot, trial, tier1, tier2, beta, enterprise plan_label: Human-readable plan name (e.g. "Personal Access", "Small Business") account_key_count: Number of account-level API keys currently issued account_key_limit: Maximum account keys allowed on this plan blueprint_count: Number of Blueprints owned by this user blueprint_limit: Maximum Blueprints allowed on this plan email: The user's email address (for reference in support) user_id: Stable user identifier trial_days_remaining: Days left on trial, if plan == "trial"; else null. It is categorised as a Read tool in the Governance Platform MCP Server, which means it retrieves data without modifying state.
Register the Governance Platform MCP server in PolicyLayer and add a rule for account_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 Governance Platform. Nothing to install.
account_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 account_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 account_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.
account_status is provided by the Governance Platform MCP server (https://app.geodesiclabs.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Governance Platform 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.