This record as markdown: /tools/io-fusionauth-mcp-api/retrievekeyswithid.md
What retrieveKeysWithId does on Fusionauth
AI agents call retrieveKeysWithId to retrieve information from Fusionauth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why retrieveKeysWithId is rated Low
This tool fetches cryptographic keys or API keys without modifying or deleting them. While key material exposure is sensitive, the tool itself performs a read-only operation with no side effects. Severity is low because the risk depends on what happens downstream with the retrieved data, not on the tool's direct action.
From the tool's definition Tool name contains 'retrieve' and description states 'Retrieves all the keys' — both indicate data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs retrieveKeysWithId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retrieveKeysWithId, this is the rule to start with:
retrieveKeysWithId 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 Fusionauth, apply this rule, and every retrieveKeysWithId call is checked against it from then on.
Questions about retrieveKeysWithId
Retrieves all the keys. It is categorised as a Read tool in the Fusionauth MCP Server, which means it retrieves data without modifying state.
Register the Fusionauth MCP server in PolicyLayer and add a rule for retrieveKeysWithId: 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 Fusionauth. Nothing to install.
retrieveKeysWithId 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 retrieveKeysWithId 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 retrieveKeysWithId. 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.
retrieveKeysWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fusionauth, and thousands of servers like it.
This server
Across the catalogue