AI agents use update_secret to create or update resources in DMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DMCP environment.
This tool modifies game state by updating a secret, which is a reversible write operation. In the context of an RPG game state manager, secrets are part of the game narrative/state that can be changed without permanent destruction. The severity is medium because misuse could disrupt game logic or reveal unintended information, but the blast radius is limited to a single game instance and the operation is reversible.
From the tool's definition Tool name 'update_secret' and description 'Update a secret' indicate modification of existing data. The verb 'update' is characteristic of Write operations that create or modify data reversibly.
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 DMCP, 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.
Update a secret. It is categorised as a Write tool in the DMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the D 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 DMCP. 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 D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, 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.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.