importKeyWithId
Import an existing RSA or EC key pair or an HMAC secret.
This record as markdown: /tools/io-fusionauth-mcp-api/importkeywithid.md
What importKeyWithId does on Fusionauth
AI agents use importKeyWithId to create or update resources in Fusionauth, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusionauth environment.
Why importKeyWithId is rated Medium
Importing cryptographic keys is a reversible Write operation (keys can be updated/replaced), but it's high-severity because misuse could introduce weak or attacker-controlled keys into the authentication/authorization infrastructure, compromising all reliant systems. Not Destructive (no deletion), not Financial, not Execute (no code execution).
From the tool's definition 'Import an existing RSA or EC key pair or an HMAC secret' — the tool creates/adds cryptographic keys to the system, modifying security-critical configuration.
Attacks that exploit this kind of access
The rule that runs importKeyWithId 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 importKeyWithId, this is the rule to start with:
importKeyWithId stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 importKeyWithId call is checked against it from then on.
Questions about importKeyWithId
Import an existing RSA or EC key pair or an HMAC secret. It is categorised as a Write tool in the Fusionauth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusionauth MCP server in PolicyLayer and add a rule for importKeyWithId: 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.
importKeyWithId is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the importKeyWithId 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 importKeyWithId. 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.
importKeyWithId 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