execute_feature · MCP Server MCP: Risk & Policy

WHAT IT DOES

What execute_feature does on MCP Server

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

The tool performs execution of features without documented safeguards, scope, or argument validation shown in the description. This fits the Execute category: actions that run code or trigger external operations whose effects depend on arguments. Severity is high because unvalidated feature execution could have wide-ranging side effects depending on what features are available on the server.

From the tool's definition Tool is named 'execute_feature' with description 'Executes a given feature'. The verb 'Executes' directly indicates arbitrary code or operation execution without specification of what 'feature' entails or its constraints.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_feature Rate-limited

execute_feature 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": {
    "execute_feature": {
      "limits": [
        {
          "counter": "execute_feature_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about execute_feature

What does the execute_feature tool do? +

Executes a given feature. It is categorised as a Execute tool in the 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 execute_feature? +

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

What risk level is execute_feature? +

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

Can I rate-limit execute_feature? +

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

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

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