get_task_detail
AI agents call get_task_detail to retrieve information from RunningHub MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A detail-retrieval function has no side effects—it reads and returns information about a task. Even without explicit description, the naming convention and context within a task management platform indicate this is a Read operation with minimal security risk (low severity). Confidence is moderate due to the empty description, but the functional context strongly supports this classification.
From the tool's definition Tool name 'get_task_detail' indicates retrieval of task information. Empty description limits precision, but the pattern of sibling tools (query_task_outputs, submit_task, sync_task_status, upload_file) and the server's purpose of 'managing task execution and…
Attacks that exploit this kind of access
get_task_detail. It is categorised as a Read tool in the RunningHub MCP Server MCP Server, which means it retrieves data without modifying state.
Register the RunningHub MCP Server 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 RunningHub MCP Server. Nothing to install.
get_task_detail 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 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.
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.
get_task_detail is provided by the RunningHub MCP Server MCP server (tolatolatop/runninghub-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 →