approve_instance_task

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-proagentstore-platform/approve-instance-task.md

WHAT IT DOES

What approve_instance_task does on ProAgentStore

AI agents invoke approve_instance_task to trigger actions in ProAgentStore. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why approve_instance_task is rated High

Approving a pending browser runtime task triggers external execution previously gated on human review.

From the tool's definition Approve a browser runtime task waiting for human approval

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs approve_instance_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For approve_instance_task, this is the rule to start with:

approve_instance_task Rate-limited

approve_instance_task stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "approve_instance_task": {
      "limits": [
        {
          "counter": "approve_instance_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every approve_instance_task call is checked against it from then on.

FAQ

Questions about approve_instance_task

What does the approve_instance_task tool do? +

Approve a browser runtime task waiting for human approval. Cannot approve a connector call held back by the per-call approval gate — those are approved by a person in the console, which is the whole point of that gate. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on approve_instance_task? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for approve_instance_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 ProAgentStore. Nothing to install.

What risk level is approve_instance_task? +

approve_instance_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit approve_instance_task? +

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

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

approve_instance_task is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ProAgentStore, and thousands of servers like it.

This server

All 243 ProAgentStore tools → High-risk tools on this server →

Across the catalogue

team_manager_approve_plan on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →