api_call · Onboarded MCP Server MCP: Risk & Policy

WHAT IT DOES

What api_call does on Onboarded MCP Server

AI agents invoke api_call to trigger actions in Onboarded MCP Server. 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.

WHY IT NEEDS A POLICY

Why api_call needs a policy

This tool executes arbitrary API calls against the Onboarded platform. While the specific APIs available depend on what spec_sync discovers, the tool itself enables execution of external operations whose effects depend on the API specifications and arguments provided.

From the tool's definition Tool description states 'Execute an API call' with explicit mention of execution. The sibling tools include financial-adjacent capabilities (ops_describe, ops_search) and destructive operations (state_delete), indicating this is a platform with significant…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

api_call Rate-limited

api_call 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": {
    "api_call": {
      "limits": [
        {
          "counter": "api_call_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Onboarded MCP Server, so you can run agents against it safely.

FAQ

Questions about api_call

What does the api_call tool do? +

Execute an API call. Requires spec_sync to have been called first. It is categorised as a Execute tool in the Onboarded MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on api_call? +

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

What risk level is api_call? +

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

Can I rate-limit api_call? +

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

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

api_call is provided by the Onboarded MCP Server MCP server (onboardedinc/onboarded-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.