Low Risk

getTask

Get a task by ID with full details, evidence, activity, and the checklist array (each item: id, text, due_date, completed_at, plus server-stamped attribution). Returns versionTimestamp; pass it to updateTask to modify. Includes percent_complete for progress tracking.

Part of the Stable Baseline server.

getTask is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE STABLE BASELINE →

Free to start. No card required.

AI agents call getTask to retrieve information from Stable Baseline without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though getTask only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTask": {}
  }
}

See the full Stable Baseline policy for all 184 tools.

Get this rule live on your own Stable Baseline server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY STABLE BASELINE →

View all 184 tools →

These attack patterns abuse exactly the kind of access getTask gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so getTask only ever does what you allow.

SECURE STABLE BASELINE →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the getTask tool do? +

Get a task by ID with full details, evidence, activity, and the checklist array (each item: id, text, due_date, completed_at, plus server-stamped attribution). Returns versionTimestamp; pass it to updateTask to modify. Includes percent_complete for progress tracking.. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTask? +

Register the Stable Baseline MCP server in PolicyLayer and add a rule for getTask: 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 Stable Baseline. Nothing to install.

What risk level is getTask? +

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

Can I rate-limit getTask? +

Yes. Add a rate_limit block to the getTask 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 getTask completely? +

Set action: deny in the PolicyLayer policy for getTask. 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 getTask? +

getTask is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Stable Baseline tool call.

Deterministic rules across all 184 Stable Baseline tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.