get_status_effect

THE RISK

Low Risk

Why get_status_effect needs a policy

This tool queries and retrieves status effect data by identifier. It performs a read-only lookup with no ability to modify game state, execute code, delete data, or affect finances. The retrieval of game metadata poses minimal security risk in an RPG context.

From the tool's definition Tool name 'get_status_effect' and description 'Get a status effect by ID' indicate a retrieval operation with no modifications or side effects.

Documented attack patterns abuse exactly the kind of access get_status_effect gives an agent:

POLICY

How to control get_status_effect

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_status_effect:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_status_effect": {}
  }
}

get_status_effect is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register DMCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More DMCP tools

Destructive cancel_event Cancel a scheduled event Destructive clear_pause_state Clear the saved pause state for a game. Use after successfully resuming to start fresh. Destructive clear_status_effects Remove all status effects from a character (or filter by type/name) Destructive delete_ability Delete an ability Destructive delete_audio Delete a stored audio file (removes file and database record) Destructive delete_character Delete a character permanently. This is IRREVERSIBLE and will remove the character and all Destructive delete_external_update Delete an external update entirely. Destructive delete_faction Delete a faction

All 204 DMCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_status_effect

What does the get_status_effect tool do? +

Get a status effect by ID. It is categorised as a Read tool in the DMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_status_effect? +

Register the D MCP server in PolicyLayer and add a rule for get_status_effect: 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.

What risk level is get_status_effect? +

get_status_effect is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_status_effect? +

Yes. Add a rate_limit block to the get_status_effect 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.

How do I block get_status_effect completely? +

Set action: deny in the PolicyLayer policy for get_status_effect. 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.

What MCP server provides get_status_effect? +

get_status_effect 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.

Enforce policy on every DMCP tool call.

Start from DMCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →