performance_monitoring · InSite MCP: Risk & Policy

WHAT IT DOES

What performance_monitoring does on InSite

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

While this tool primarily reads performance data (which might suggest 'Read'), the terms 'profiling' and 'optimization insights' imply active execution of instrumentation or tracing code within the browser runtime. Performance profiling typically requires executing instrumentation hooks and sampling code paths—actions that modify browser state transiently but depend on execution context.

From the tool's definition Tool description states 'Real-time performance monitoring, profiling, and optimization insights' — 'profiling' indicates active execution and inspection of runtime behavior.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

performance_monitoring Rate-limited

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

FAQ

Questions about performance_monitoring

What does the performance_monitoring tool do? +

Real-time performance monitoring, profiling, and optimization insights. It is categorised as a Execute tool in the InSite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on performance_monitoring? +

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

What risk level is performance_monitoring? +

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

Can I rate-limit performance_monitoring? +

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

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

performance_monitoring is provided by the InSite MCP server (jowharshamshiri/insite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.