List all external updates for a game with optional status filter.
AI agents call list_external_updates 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 and retrieves existing game update data, applying only an optional status filter. It performs no mutations, deletions, code execution, or financial operations. The worst-case misuse would be unauthorized information disclosure within a game's state, which is bounded to the RPG context and represents minimal real-world impact.
From the tool's definition Tool name contains 'list' and description states 'List all external updates' with optional filtering. The verb 'list' indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_external_updates 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 list_external_updates:
{
"version": "1",
"default": "deny",
"tools": {
"list_external_updates": {}
}
}list_external_updates 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.
List all external updates for a game with optional status filter. 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 list_external_updates: 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.
list_external_updates 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 list_external_updates 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 list_external_updates. 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.
list_external_updates 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.