generate_performance_report

THE RISK

Low Risk

Why generate_performance_report needs a policy

The tool generates a performance analysis report, which is a read/query operation that retrieves and aggregates performance statistics. It does not modify, delete, or execute data. Similar sibling tools like get_query_stats and get_schema_statistics further suggest this is a reporting/read operation. No side effects are implied.

From the tool's definition Generate performance analysis report

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

POLICY

How to control generate_performance_report

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 generate_performance_report:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_performance_report": {}
  }
}

generate_performance_report is read-only, so it stays allowed — but 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.

CAP 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 Execute start_performance_monitoring Start performance monitoring 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

All 11 MCP SQL Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about generate_performance_report

What does the generate_performance_report tool do? +

Generate performance analysis report. It is categorised as a Read tool in the MCP SQL Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on generate_performance_report? +

Register the MCP SQL Server MCP server in PolicyLayer and add a rule for generate_performance_report: 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 generate_performance_report? +

generate_performance_report is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit generate_performance_report? +

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

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

generate_performance_report 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 →