List all indexed canonical mods with their example counts and descriptions. Use this to discover what mods are available for examples.
AI agents call list_canonical_mods to retrieve information from Mcmodding without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries information about available mods from an indexed documentation database. It has no side effects, does not modify or delete data, does not execute code, and does not involve financial operations. It is a straightforward informational lookup mechanism, making it a Read category tool with low severity risk.
From the tool's definition Tool description states it 'List[s] all indexed canonical mods with their example counts and descriptions' and is explicitly intended to 'discover what mods are available'.
Documented attack patterns abuse exactly the kind of access list_canonical_mods gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcmodding, and nothing reaches the server without passing your rules. This is the rule we recommend for list_canonical_mods:
{
"version": "1",
"default": "deny",
"tools": {
"list_canonical_mods": {}
}
}list_canonical_mods 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 indexed canonical mods with their example counts and descriptions. Use this to discover what mods are available for examples. It is categorised as a Read tool in the Mcmodding MCP Server, which means it retrieves data without modifying state.
Register the Mcmodding MCP server in PolicyLayer and add a rule for list_canonical_mods: 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 Mcmodding. Nothing to install.
list_canonical_mods 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_canonical_mods 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_canonical_mods. 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_canonical_mods is provided by the Mcmodding MCP server (ogmatrix/mcmodding-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Mcmodding tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Mcmodding tools catalogued and risk-classified — across an index of 42,500+ MCP servers.