Low Risk

generate_health_report

generate_health_report

How to control generate_health_report ↓

What generate_health_report does on Amazon Redshift MCP Server

AI agents call generate_health_report to retrieve information from Amazon Redshift MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why generate_health_report needs a policy

The name 'generate_health_report' strongly implies a read/reporting operation that queries system health metrics and produces a report without modifying data. However, the empty description lowers confidence. In context of an Amazon Redshift MCP server, health reports are typically read-only diagnostic queries. Severity is medium because misuse could expose sensitive database performance or configuration data.

From the tool's definition Tool name: 'generate_health_report' — no description provided

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

How to control generate_health_report

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_health_report": {}
  }
}

generate_health_report is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon Redshift MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about generate_health_report

What does the generate_health_report tool do? +

generate_health_report. It is categorised as a Read tool in the Amazon Redshift MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on generate_health_report? +

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

What risk level is generate_health_report? +

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

Can I rate-limit generate_health_report? +

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

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

generate_health_report is provided by the Amazon Redshift MCP Server MCP server (awslabs.redshift-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon Redshift MCP Server tool call.

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

Free to start. No card required.

805 Amazon Redshift MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.