generate_health_report · AWS IoT SiteWise MCP Server MCP

WHAT IT DOES

What generate_health_report does on AWS IoT SiteWise MCP Server

AI agents call generate_health_report as a supporting operation in AWS IoT SiteWise MCP Server workflows.

WHY IT NEEDS A POLICY

Why generate_health_report needs a policy

With no description available, classification relies solely on the tool name. 'Generate health report' most likely reads system health data and produces a report (a Read operation), but without confirmation the confidence is low. Defaulting to Other given insufficient evidence, with low severity as report generation is typically non-destructive.

From the tool's definition Tool description is empty and uninformative; the name 'generate_health_report' suggests reading/generating a report but cannot be confirmed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_health_report Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_health_report": {
      "limits": [
        {
          "counter": "generate_health_report_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches AWS IoT SiteWise MCP Server, so you can run agents against it safely.

FAQ

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 AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on generate_health_report? +

Register the AWS IoT SiteWise 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 AWS IoT SiteWise MCP Server. 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 AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.