Low Risk

get_task

Get a specific task by project ID and task ID

How to control get_task ↓

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

Low Risk

This tool retrieves task information by ID parameters. It performs a query operation with no side effects—no data is created, modified, deleted, or executed. It simply returns existing task data. Classification as Read is appropriate, and severity is low as data retrieval poses minimal risk even if misused by an agent.

From the tool's definition Tool name 'get_task' and description 'Get a specific task by project ID and task ID' indicate data retrieval without modification. The verb 'Get' and context of querying by identifiers align with read-only operations.

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 Roadmap Skill, and nothing reaches the server without passing your rules. This is the rule we recommend for get_task:

policy.json
{
  "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.

  1. Create a free account and register Roadmap Skill — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_task tool do? +

Get a specific task by project ID and task ID. It is categorised as a Read tool in the Roadmap Skill MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task? +

Register the Roadmap Skill 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 Roadmap Skill. Nothing to install.

What risk level is get_task? +

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

Can I rate-limit get_task? +

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.

How do I block get_task completely? +

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.

What MCP server provides get_task? +

get_task is provided by the Roadmap Skill MCP server (shiquda/roadmap-skill). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Roadmap Skill tool call.

Deterministic rules across all 32 Roadmap Skill tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

32 Roadmap Skill tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.