call_nested_mcp · MCPify MCP: Risk & Policy

WHAT IT DOES

What call_nested_mcp does on MCPify

AI agents invoke call_nested_mcp to trigger actions in MCPify. 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 call_nested_mcp needs a policy

The name 'call_nested_mcp' strongly suggests executing or triggering operations on a nested MCP server, which falls under Execute as it runs external operations. The context of sibling tools like 'how_to_nest_mcps' and 'authenticated_operation' supports this interpretation.

From the tool's definition Tool name: 'call_nested_mcp' — implies invoking or executing a nested MCP (Model Context Protocol) server/tool. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

call_nested_mcp Rate-limited

call_nested_mcp 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_nested_mcp": {
      "limits": [
        {
          "counter": "call_nested_mcp_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 MCPify, so you can run agents against it safely.

FAQ

Questions about call_nested_mcp

What does the call_nested_mcp tool do? +

call_nested_mcp. It is categorised as a Execute tool in the MCPify 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_nested_mcp? +

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

What risk level is call_nested_mcp? +

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

Can I rate-limit call_nested_mcp? +

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

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

call_nested_mcp is provided by the MCPify MCP server (sancovp/mcpify). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

call_nested_mcp is one line of MCPify's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →