Rotate one of the caller's API keys. The old key stops working immediately; a new key with the same scope is issued. The new key inherits the old key's scope: - An account-level key rotates to another account-level key. - A Blueprint-scoped key rotates to a key for the same Blueprint. The target ...
Risk signalsHandles credentials or secrets (api_key)
Part of the Governance Platform server.
Free to start. No card required.
AI agents call rotate_api_key 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 rotate_api_key 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": {
"rotate_api_key": {}
}
}See the full Governance Platform policy for all 31 tools.
These attack patterns abuse exactly the kind of access rotate_api_key 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.
Rotate one of the caller's API keys. The old key stops working immediately; a new key with the same scope is issued. The new key inherits the old key's scope: - An account-level key rotates to another account-level key. - A Blueprint-scoped key rotates to a key for the same Blueprint. The target key can be specified two ways: - As the full key string (gai_...) — useful if you just received it. - As a key_id (SHA-256 hash from list_api_keys) — useful when you only have the masked version. Either is accepted. Args: api_key: GeodesicAI account-level API key (starts with gai_). Must be an account key. key_to_rotate: Either the full API key string OR the key_id (SHA-256 hex hash) returned by list_api_keys. Returns: status: "ok" | "ERROR" api_key: the new key string (copy this immediately) type: "account" | "blueprint" intent: Blueprint folder name, or empty for account keys. 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 rotate_api_key: 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.
rotate_api_key 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 rotate_api_key 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 rotate_api_key. 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.
rotate_api_key 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.