AI agents call get_task_details to retrieve information from MCP Orchestrator Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries task information without creating, modifying, deleting, or executing any operations. It has no side effects on the system state. While it exists within a task orchestration system, the tool itself only accesses and returns data about tasks, making it a Read category tool with low severity since unauthorized access to task details represents limited blast radius compared to tools that…
From the tool's definition Tool name 'get_task_details' and description 'Get details of a specific task' indicate data retrieval with no modification or execution. The verb 'get' and the query nature of retrieving task information align with read-only operations.
Documented attack patterns abuse exactly the kind of access get_task_details gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Orchestrator Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_task_details": {}
}
}get_task_details is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get details of a specific task. It is categorised as a Read tool in the MCP Orchestrator Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Orchestrator Server MCP server in PolicyLayer and add a rule for get_task_details: 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 Orchestrator Server. Nothing to install.
get_task_details 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_details 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_details. 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_details is provided by the MCP Orchestrator Server MCP server (mokafari/orchestrator-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Orchestrator Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 MCP Orchestrator Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.