campaign_research_list
AI agents call campaign_research_list 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 tool name contains 'list', a standard read operation verb. No description is provided to contradict this, but the sibling tools follow a consistent pattern where 'list' and 'get' operations are read-only data retrievals. Confidence is moderately high (0.75) due to empty description, but the naming convention and server context strongly support Read category.
From the tool's definition Tool name 'campaign_research_list' uses the verb 'list', which retrieves data without modification. The server context shows this is a task/campaign management system, and 'list' operations across sibling tools (campaign_list,…
Attacks that exploit this kind of access
campaign_research_list. 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_research_list: 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_research_list 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_research_list 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_research_list. 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_research_list 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 →