request_capability

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 52 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/request-capability.md

WHAT IT DOES

What request_capability does on VaultPilot MCP

AI agents use request_capability to create or update resources in VaultPilot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultPilot MCP environment.

Parameter	Type	Required	Description
`context`	object	—
`summary`	string	Yes	One-line title of the missing capability (used as the GitHub issue title). E.g. 'Support Aerodrome LP positions on Base' or 'Add Pendle PT/YT position reader'.
`category`	string	—	Rough bucket to help triage.
`agentName`	string	—	MCP client identifier (e.g. 'Claude Code', 'Cursor'). Helps triage.
`description`	string	Yes	What the user asked for, what the agent tried, what's missing, and why the existing tools don't cover it. Include protocol name, chain, contract addresses, and

Parameters from the server's own tool schema.

RISK

Why request_capability is rated Medium

In the default case this is effectively a Read/Other operation (just constructs a URL), but when the optional feedback endpoint is configured it transmits data to an external HTTP endpoint, making it a Write operation. Since the tool can operate in either mode and the more impactful path is Write, Write is the appropriate category.

From the tool's definition 'posts directly to that proxy instead' and 'By default this returns a pre-filled GitHub issue URL — NO data is transmitted; the user must click through to submit' — when VAULTPILOT_FEEDBACK_ENDPOINT is configured, it actively POSTs data externally; otherwise…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs request_capability safely

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

request_capability Rate-limited

request_capability stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "request_capability": {
      "limits": [
        {
          "counter": "request_capability_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about request_capability

What does the request_capability tool do? +

File a capability request against the vaultpilot-mcp GitHub repository when the user asks for something this server cannot do (e.g. an unsupported protocol, chain, token, or missing tool). USE ONLY AFTER confirming no existing tool can accomplish the task. By default this returns a pre-filled GitHub issue URL — NO data is transmitted; the user must click through to submit. If the operator has configured VAULTPILOT_FEEDBACK_ENDPOINT, it posts directly to that proxy instead. Rate-limited per install (30s between calls, 3/hour, 10/day, 7-day dedupe on identical summaries). Write clear, actionable summaries — this lands in a real issue tracker read by humans. It is categorised as a Write tool in the VaultPilot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does request_capability accept? +

request_capability accepts 5 parameters: context, summary, category, agentName, description. Required: summary, description. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on request_capability? +

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

What risk level is request_capability? +

request_capability is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit request_capability? +

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

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

request_capability is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →