Updates a secret in a project
AI agents use update_secret to create or update resources in Keyshade — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Keyshade environment.
This tool modifies secrets within Keyshade's secrets management platform. While secrets are sensitive and critical to infrastructure security, the operation is reversible (the secret can be updated again or reverted). It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute).
From the tool's definition Tool name 'update_secret' and description 'Updates a secret in a project' indicate modification of existing secrets management data. This is a reversible write operation on sensitive secret infrastructure.
Documented attack patterns abuse exactly the kind of access update_secret gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Keyshade, and nothing reaches the server without passing your rules. This is the rule we recommend for update_secret:
{
"version": "1",
"default": "deny",
"tools": {
"update_secret": {
"limits": [
{
"counter": "update_secret_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_secret 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.
Updates a secret in a project. It is categorised as a Write tool in the Keyshade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Keyshade MCP server in PolicyLayer and add a rule for update_secret: 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 Keyshade. Nothing to install.
update_secret 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 update_secret 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 update_secret. 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.
update_secret is provided by the Keyshade MCP server (keyshade-xyz/keyshade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Keyshade, 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.
44 Keyshade tools catalogued and risk-classified — across an index of 43,000+ MCP servers.