campaign_get_state_snapshot
AI agents call campaign_get_state_snapshot to retrieve information from Task Crusader MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' verb and '_snapshot' suffix strongly suggest this tool retrieves a point-in-time view of campaign state without modification. Sibling tools confirm a pattern of read-only query operations. While the empty description reduces confidence slightly, the naming convention and context place this clearly in the Read category with no side effects.
From the tool's definition Tool name 'campaign_get_state_snapshot' uses 'get' verb, indicating retrieval/query operation. Description is empty, but name pattern and sibling tools (campaign_details, campaign_get_progress_summary, campaign_list) suggest this retrieves read-only state…
Attacks that exploit this kind of access
campaign_get_state_snapshot. It is categorised as a Read tool in the Task Crusader MCP MCP Server, which means it retrieves data without modifying state.
Register the Task Crusader MCP server in PolicyLayer and add a rule for campaign_get_state_snapshot: 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 Task Crusader MCP. Nothing to install.
campaign_get_state_snapshot 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 campaign_get_state_snapshot 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 campaign_get_state_snapshot. 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.
campaign_get_state_snapshot is provided by the Task Crusader MCP server (mcrescenzo/task-crusader-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 →