Low Risk

generate_health_report

generate_health_report

How to control generate_health_report ↓

What generate_health_report does on Awslabs Amazon Sns Sqs

AI agents call generate_health_report as a supporting operation in Awslabs Amazon Sns Sqs workflows.

Low Risk

Why generate_health_report needs a policy

With no description available, classification is based solely on the tool name. 'Generate health report' implies reading system status and producing a report, which would be a Read operation with low severity. However, confidence is very low due to the absence of any description. Assigning 'Other' to reflect the uncertainty, though Read would be the most likely category if the name is taken at face value.

From the tool's definition Tool description is empty and uninformative; the name 'generate_health_report' suggests a read/reporting operation but cannot be confirmed.

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 Awslabs Amazon Sns Sqs, 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": {
      "limits": [
        {
          "counter": "generate_health_report_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

generate_health_report gets a rate cap, and everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Awslabs Amazon Sns Sqs — 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.
SET A RULE FOR 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 Other tool in the Awslabs Amazon Sns Sqs MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on generate_health_report? +

Register the Awslabs Amazon Sns Sqs 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 Awslabs Amazon Sns Sqs. Nothing to install.

What risk level is generate_health_report? +

generate_health_report is a Other 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 Awslabs Amazon Sns Sqs MCP server (awslabs.amazon-sns-sqs-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 Awslabs Amazon Sns Sqs tool call.

Start from Awslabs Amazon Sns Sqs, 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 Awslabs Amazon Sns Sqs 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.