Get the total stat modifiers from all status effects on a character
AI agents call get_effective_modifiers to retrieve information from DMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries game state (character status effects and their modifiers) to return computed values. It has no side effects, does not create, modify, or delete data, and does not execute arbitrary code or external operations. It is a straightforward data retrieval operation typical of the Read category.
From the tool's definition Tool name 'get_effective_modifiers' and description 'Get the total stat modifiers from all status effects on a character' indicate a read-only query operation that retrieves and calculates values from existing game state without modification.
Documented attack patterns abuse exactly the kind of access get_effective_modifiers 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 get_effective_modifiers:
{
"version": "1",
"default": "deny",
"tools": {
"get_effective_modifiers": {}
}
}get_effective_modifiers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the total stat modifiers from all status effects on a character. It is categorised as a Read tool in the DMCP MCP Server, which means it retrieves data without modifying state.
Register the D MCP server in PolicyLayer and add a rule for get_effective_modifiers: 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.
get_effective_modifiers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_effective_modifiers 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 get_effective_modifiers. 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.
get_effective_modifiers 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.