Returns full details for requested tasks
AI agents call task_info to retrieve information from Mcp Task Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
taskIDs | array | Yes | A list of task IDs to retrieve information for |
Parameters from the server's own tool schema.
The tool only fetches and returns information about tasks. No creation, modification, deletion, or execution is involved. Misuse risk is minimal as it only exposes task details.
From the tool's definition 'Returns full details for requested tasks' — retrieves existing task data with no side effects
Attacks that exploit this kind of access
Returns full details for requested tasks. It is categorised as a Read tool in the Mcp Task Manager MCP Server, which means it retrieves data without modifying state.
task_info accepts 1 parameter: taskIDs. Required: taskIDs. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Task Manager MCP server in PolicyLayer and add a rule for task_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 Mcp Task Manager. Nothing to install.
task_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_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_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_info is provided by the Mcp Task Manager MCP server (@blizzy/mcp-task-manager). 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 →