Low Risk

get_task

查询任务状态和最终结果

How to control get_task ↓

What get_task does on Openaaas Mcp Adapter

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

Low Risk

Why get_task needs a policy

This tool queries and retrieves existing task information (status and results). It has no side effects, does not modify or delete data, does not execute code, and does not involve financial operations. It is a straightforward read/retrieval operation typical of status-checking functionality in a task management system.

From the tool's definition Tool name 'get_task' and description '查询任务状态和最终结果' (query task status and final results) indicate retrieval of task metadata and results without modification.

Documented attack patterns abuse exactly the kind of access get_task gives an agent:

How to control get_task

PolicyLayer is an MCP gateway — it sits between your AI agents and Openaaas Mcp Adapter, 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 Openaaas Mcp Adapter — 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.

Related tools and policies

Go deeper

Questions about get_task

What does the get_task tool do? +

查询任务状态和最终结果. It is categorised as a Read tool in the Openaaas Mcp Adapter MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_task? +

Register the Openaaas Mcp Adapter 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 Openaaas Mcp Adapter. 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 Openaaas Mcp Adapter MCP server (wolido/openaaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Openaaas Mcp Adapter tool call.

Start from Openaaas Mcp Adapter, 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.

16 Openaaas Mcp Adapter tools catalogued and risk-classified — across an index of 43,000+ 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.