list_campaigns
AI agents call list_campaigns to retrieve information from RPG Ledger MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries campaign data without side effects. The empty description prevents deeper analysis, but the naming convention and context strongly indicate a read-only operation. No deletion, modification, execution, or financial impact is suggested. Severity is low because listing campaigns poses minimal risk—the worst misuse is information disclosure of existing campaign metadata.
From the tool's definition Tool name 'list_campaigns' indicates a retrieval operation with no mutation capability. The server context describes managing campaign state, and 'list' is a classic Read operation pattern (search, list, get, fetch per the classification rules).
Attacks that exploit this kind of access
list_campaigns. It is categorised as a Read tool in the RPG Ledger MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RPG Ledger MCP Server MCP server in PolicyLayer and add a rule for list_campaigns: 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 RPG Ledger MCP Server. Nothing to install.
list_campaigns 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_campaigns 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_campaigns. 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_campaigns is provided by the RPG Ledger MCP Server MCP server (sepa79/rpg-ledger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →