pilotgentic_call_skill · PilotGentic MCP: Risk & Policy

WHAT IT DOES

What pilotgentic_call_skill does on PilotGentic

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

This tool acts as a dispatcher that executes arbitrary named skills, making its effective category and severity dependent on what skill is invoked. Since it can trigger any available skill (including browser control, system interactions, and other agentic operations as described in the server description), the most severe plausible category is Execute.

From the tool's definition 'Call a docked PilotGentic skill by tool name' — invokes external skills/tools by name, triggering operations whose effects depend entirely on which skill is called and its arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pilotgentic_call_skill Rate-limited

pilotgentic_call_skill 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": {
    "pilotgentic_call_skill": {
      "limits": [
        {
          "counter": "pilotgentic_call_skill_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 PilotGentic, so you can run agents against it safely.

FAQ

Questions about pilotgentic_call_skill

What does the pilotgentic_call_skill tool do? +

Call a docked PilotGentic skill by tool name. Use pilotgentic_list_skills first to see what is available. Example tools: browser_ext_stats (Browser Extension live stats from current browser tab). It is categorised as a Execute tool in the PilotGentic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pilotgentic_call_skill? +

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

What risk level is pilotgentic_call_skill? +

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

Can I rate-limit pilotgentic_call_skill? +

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

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

pilotgentic_call_skill is provided by the PilotGentic MCP server (@pilotgentic/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.