get_task_detail

get_task_detail

Server Tick kpihx/tick-mcp
Category Read
Risk class Low
Parameters 00 required

What get_task_detail does on Tick

AI agents call get_task_detail to retrieve information from Tick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_task_detail needs a policy

The tool name strongly suggests a retrieval operation that queries task information. No description is available to provide contradictory evidence. Confidence is slightly reduced (0.85 rather than higher) due to the empty description, but the naming convention and context within a task management system makes Read the most appropriate classification.

From the tool's definition Tool name 'get_task_detail' follows a 'get_*' pattern, which retrieves data without modification. The sibling tools include destructive actions (batch_delete_tasks, complete_task) and write operations (create_habit, create_project), but get_task_detail aligns…

Questions about get_task_detail

What does the get_task_detail tool do? +

get_task_detail. It is categorised as a Read tool in the Tick MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task_detail? +

Register the Tick MCP server in PolicyLayer and add a rule for get_task_detail: 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 Tick. Nothing to install.

What risk level is get_task_detail? +

get_task_detail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_task_detail? +

Yes. Add a rate_limit block to the get_task_detail 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.

How do I block get_task_detail completely? +

Set action: deny in the PolicyLayer policy for get_task_detail. 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.

What MCP server provides get_task_detail? +

get_task_detail is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.