get_campaign
AI agents call get_campaign 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.
The 'get_' prefix and campaign context indicate this tool retrieves RPG campaign data without modifying it. Given the server manages campaign state through dedicated mutation tools (create_campaign, create_character, delete_location) that appear in the sibling tools list, get_campaign is almost certainly a read operation.
From the tool's definition Tool name 'get_campaign' follows standard read-only naming convention (get/fetch pattern). No description provided, but context from server capabilities indicates this retrieves campaign state data including characters, inventory, quests, and logs.
Attacks that exploit this kind of access
get_campaign. 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 get_campaign: 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.
get_campaign 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 get_campaign 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 get_campaign. 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.
get_campaign 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 →