Store an API_KEY credential. Use just
AI agents use vault_storeApiKey to create or update resources in Mailgent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mailgent MCP Server environment.
This tool creates or updates a stored credential (API key) in a vault, which is a Write operation. The severity is high because misuse could allow an attacker to store malicious or unauthorized credentials, potentially enabling impersonation or unauthorized access to external services. The description is truncated ('Use just'), which slightly lowers confidence, but the core action of storing an API key is clear.
From the tool's definition 'Store an API_KEY credential' — the tool writes/persists an API key into a secure vault.
Attacks that exploit this kind of access
Store an API_KEY credential. Use just. It is categorised as a Write tool in the Mailgent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for vault_storeApiKey: 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 Mailgent MCP Server. Nothing to install.
vault_storeApiKey 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 vault_storeApiKey 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 vault_storeApiKey. 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.
vault_storeApiKey is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →