Store a secret value
AI agents use secrets.put to create or update resources in MCP Fullstack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Fullstack environment.
This tool writes/stores a secret value (e.g., API keys, passwords, credentials) into a secrets management system. It creates or updates sensitive data reversibly. Misuse by an AI agent could result in overwriting critical secrets or storing malicious values, making severity high.
From the tool's definition Store a secret value
Attacks that exploit this kind of access
Store a secret value. It is categorised as a Write tool in the MCP Fullstack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Fullstack MCP server in PolicyLayer and add a rule for secrets.put: 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 MCP Fullstack. Nothing to install.
secrets.put 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 secrets.put 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 secrets.put. 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.
secrets.put is provided by the MCP Fullstack MCP server (jacobfv/mcp-fullstack). 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 →