Retrieves complete information about a specific task when you know its exact ID. This tool provides direct access to a single task
AI agents call get-task-by-id to retrieve information from Specifai MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward data retrieval operation that queries and returns information about a task without modifying, executing, or deleting anything. It matches the Read category definition: 'retrieves or queries data; no side effects'. The low severity reflects minimal blast radius—an agent can only view existing task information, not alter systems or cause irreversible changes.
From the tool's definition Tool description states it 'Retrieves complete information about a specific task' and server description confirms the server 'exposes tools to read all documents'.
Documented attack patterns abuse exactly the kind of access get-task-by-id gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Specifai MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get-task-by-id:
{
"version": "1",
"default": "deny",
"tools": {
"get-task-by-id": {}
}
} get-task-by-id 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.
Retrieves complete information about a specific task when you know its exact ID. This tool provides direct access to a single task. It is categorised as a Read tool in the Specifai MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Specifai MCP Server MCP server in PolicyLayer and add a rule for get-task-by-id: 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 Specifai MCP Server. Nothing to install.
get-task-by-id 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-by-id 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-by-id. 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-by-id is provided by the Specifai MCP Server MCP server (presidio-oss/specifai-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Specifai MCP 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.
13 Specifai MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.