Generate a user key for RBAC access.
AI agents use generate-user-key to create or update resources in Secure Embedding MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Secure Embedding MCP Server environment.
This tool creates a new security credential (user key) that can be used to grant system access. While it doesn't modify existing data or delete anything, generating credentials is a reversible write operation that affects authentication state. The severity is medium because misuse could grant unintended access, but the actual impact depends on how the key is used and what permissions it carries.
From the tool's definition Tool generates a new user key, which creates or modifies access control data. Description states it 'Generate[s] a user key for RBAC access,' indicating creation of authentication/authorization credentials.
Documented attack patterns abuse exactly the kind of access generate-user-key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Secure Embedding MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate-user-key:
{
"version": "1",
"default": "deny",
"tools": {
"generate-user-key": {
"limits": [
{
"counter": "generate-user-key_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}generate-user-key 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.
Free to start. No card required.
Generate a user key for RBAC access. It is categorised as a Write tool in the Secure Embedding MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Secure Embedding MCP Server MCP server in PolicyLayer and add a rule for generate-user-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 Secure Embedding MCP Server. Nothing to install.
generate-user-key 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 generate-user-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 generate-user-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.
generate-user-key is provided by the Secure Embedding MCP Server MCP server (mirrorsecai/mirror-vectax-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Secure Embedding MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Secure Embedding MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.