task_show
AI agents call task_show 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.
Despite the empty description, the naming convention ('show') and the prevalence of read-only query tools among siblings (get_*, list, details, overview) strongly indicate this tool retrieves or displays task data without side effects. Confidence is moderately high but not absolute due to missing description. If this tool had side effects (e.g., marking tasks complete), it would be Write; if destructive, Destructive.
From the tool's definition Tool name 'task_show' combined with server context (task management for projects) and sibling tools including 'campaign_get_progress_summary', 'campaign_get_state_snapshot', and 'campaign_details' suggest this retrieves task information.
Attacks that exploit this kind of access
task_show. 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 task_show: 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.
task_show 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 task_show 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 task_show. 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.
task_show 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 →