mcp_performance_metrics

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke mcp_performance_metrics to trigger processes or run actions in Ae. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON MCP_PERFORMANCE_METRICS

mcp_performance_metrics can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

ae.yaml

tools:
  mcp_performance_metrics:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Ae policy for all 35 tools.

// DETAILS

Tool Name mcp_performance_metrics

Category Execute

MCP Server Ae MCP Server

Risk Level High

// MORE AE TOOLS

Destructive ae_delete_layer Destructive ae_remove_effect Execute ae_animate_property Write ae_add_audio_markers Write ae_add_expression Write ae_add_keyframe Write ae_add_text_animator Write ae_animate_camera

View all 35 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like mcp_performance_metrics have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records getting_started

// IN CONTEXT OF HIGH RISK

mcp_performance_metrics is one of the high-risk operations in Ae. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the mcp_performance_metrics tool do? +

Get detailed performance metrics and statistics. It is categorised as a Execute tool in the Ae MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mcp_performance_metrics? +

Add a rule in your Intercept YAML policy under the tools section for mcp_performance_metrics. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ae MCP server.

What risk level is mcp_performance_metrics? +

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

Can I rate-limit mcp_performance_metrics? +

Yes. Add a rate_limit block to the mcp_performance_metrics rule in your Intercept 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 mcp_performance_metrics completely? +

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

mcp_performance_metrics is provided by the Ae MCP server (ae-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.