call_instance_tool

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/call-instance-tool.md

WHAT IT DOES

What call_instance_tool does on ProAgentStore

AI agents invoke call_instance_tool 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 call_instance_tool is rated High

Invokes external connector tools whose effects depend on arguments; high blast radius if misused.

From the tool's definition Invoke a connector tool on instances; arbitrary tool invocation via wrapper

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs call_instance_tool 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 call_instance_tool, this is the rule to start with:

call_instance_tool Rate-limited

call_instance_tool 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": {
    "call_instance_tool": {
      "limits": [
        {
          "counter": "call_instance_tool_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 call_instance_tool call is checked against it from then on.

FAQ

Questions about call_instance_tool

What does the call_instance_tool tool do? +

Invoke a connector tool (e.g. github_workflow_runs, github_list_issues) on one of your instances. This is a two-step wrapper: first call list_instance_tools with allowed_only:true and schemas:true, find the target tool, then pass. 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 call_instance_tool? +

Register the ProAgentStore MCP server in PolicyLayer and add a rule for call_instance_tool: 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 call_instance_tool? +

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

Can I rate-limit call_instance_tool? +

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

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

call_instance_tool 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

call_rpc on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

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