task_get_dependency_info
AI agents call task_get_dependency_info 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_' prefix combined with 'dependency_info' strongly suggests this retrieves/queries dependency metadata without modifying state. The lack of description lowers confidence slightly, but the pattern of read-only sibling tools (campaign_get_*) provides supporting context. No evidence of side effects, code execution, or data destruction. Classified as Read with low severity due to minimal blast radius for misuse.
From the tool's definition Tool name 'task_get_dependency_info' indicates retrieval of dependency information; no description provided but the name suggests a query operation.
Attacks that exploit this kind of access
task_get_dependency_info. 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_get_dependency_info: 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_get_dependency_info 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_get_dependency_info 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_get_dependency_info. 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_get_dependency_info 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 →