List random tables in a game
AI agents call list_random_tables 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 retrieves and displays random tables from a game state without creating, modifying, deleting, or executing any operations. It has no side effects on the game world or data. The blast radius of misuse is minimal—an agent could only view random table definitions, which poses no risk to game integrity or player data.
From the tool's definition Tool name 'list_random_tables' and description 'List random tables in a game' indicate data retrieval without modification. The verb 'list' is a classic read operation that queries and returns information about game random tables.
Documented attack patterns abuse exactly the kind of access list_random_tables 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_random_tables:
{
"version": "1",
"default": "deny",
"tools": {
"list_random_tables": {}
}
}list_random_tables 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 random tables in a game. 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_random_tables: 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_random_tables 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_random_tables 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_random_tables. 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_random_tables 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.