Reads and returns a specific task by ID. Shows all metadata including frontmatter, description, subtasks, and notes.
AI agents call get_task to retrieve information from Project MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves task information by identifier. It accesses existing data structures (metadata, frontmatter, descriptions, subtasks, notes) without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal—an agent could only retrieve unintended task information, which is an information disclosure risk at most.
From the tool's definition Tool name 'get_task' and description 'Reads and returns a specific task by ID' clearly indicate data retrieval with no side effects. The description explicitly states it 'Reads' data and returns existing task metadata without modification.
Documented attack patterns abuse exactly the kind of access get_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task:
{
"version": "1",
"default": "deny",
"tools": {
"get_task": {}
}
}get_task 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.
Reads and returns a specific task by ID. Shows all metadata including frontmatter, description, subtasks, and notes. It is categorised as a Read tool in the Project MCP MCP Server, which means it retrieves data without modifying state.
Register the Project MCP server in PolicyLayer and add a rule for get_task: 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 Project MCP. Nothing to install.
get_task 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 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. 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 is provided by the Project MCP server (pouyanafisi/project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project MCP, 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.
42 Project MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.