rotate_api_key
Replace the API key making this call with a fresh one carrying the same scopes. WARNING: this IRREVERSIBLY deactivates the current key the moment it succeeds — every other caller using that key stops working immediately, so do not call it on a shared credential. The new key is returned exactly on...
This record as markdown: /tools/com-meta-council-decision-intelligence/rotate-api-key.md
What rotate_api_key does on Meta Council
AI agents call rotate_api_key to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
expires_in_days | integer | — | Lifetime of the replacement key in days (default 90). |
Parameters from the server's own tool schema.
Why rotate_api_key is rated Low
Even though rotate_api_key only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs rotate_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rotate_api_key, this is the rule to start with:
rotate_api_key is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every rotate_api_key call is checked against it from then on.
Questions about rotate_api_key
Replace the API key making this call with a fresh one carrying the same scopes. WARNING: this IRREVERSIBLY deactivates the current key the moment it succeeds — every other caller using that key stops working immediately, so do not call it on a shared credential. The new key is returned exactly once in the response and cannot be retrieved again. A delegated child key cannot rotate itself. Requires API-key authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
rotate_api_key accepts 1 parameter: expires_in_days. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council 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 Meta Council. 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 Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue