start_performance_monitoring

THE RISK

High Risk

Why start_performance_monitoring needs a policy

This tool initiates an external operation (performance monitoring) on the database system rather than passively retrieving data. It is Execute rather than Write because it does not create/modify persistent data records, but instead activates a monitoring process. It is not Destructive (no data loss), Financial (no monetary impact), or Destructive.

From the tool's definition Tool starts performance monitoring on the SQL database server. The description 'Start performance monitoring' indicates it triggers an external operation (enabling monitoring/instrumentation on the database system).

Documented attack patterns abuse exactly the kind of access start_performance_monitoring gives an agent:

POLICY

How to control start_performance_monitoring

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP SQL Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_performance_monitoring:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_performance_monitoring": {
      "limits": [
        {
          "counter": "start_performance_monitoring_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

start_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.

Create a free account and register MCP SQL Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More MCP SQL Server tools

Destructive clear_caches Initialize cache data Execute execute_query Execute SQL queries Execute start_batch_processing Process multiple queries in batch Read describe_table Get structure of a specific table Read get_connection_pool_status Get database connection pool status Read get_query_stats Get query execution statistics Read get_schema Get database schema information Read get_schema_statistics Get schema statistics information

All 11 MCP SQL Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in MCP SQL Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about start_performance_monitoring

What does the start_performance_monitoring tool do? +

Start performance monitoring. It is categorised as a Execute tool in the MCP SQL 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 start_performance_monitoring? +

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

What risk level is start_performance_monitoring? +

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

Can I rate-limit start_performance_monitoring? +

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

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

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

Enforce policy on every MCP SQL Server tool call.

Start from MCP SQL Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →