describe_severity_levels

describe_severity_levels

Server AWS IoT SiteWise MCP Server awslabs.aws-iot-sitewise-mcp-server
Category Read
Risk class Low
Parameters 00 required

What describe_severity_levels does on AWS IoT SiteWise MCP Server

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

Why describe_severity_levels needs a policy

The 'describe' prefix strongly indicates a read-only operation that retrieves information about severity levels—likely configuration or reference data. No indication of data modification, deletion, code execution, or financial operations. The empty description prevents higher confidence, but the naming convention is a reliable signal in AWS contexts.

From the tool's definition Tool name 'describe_severity_levels' suggests retrieval of metadata or configuration data. The 'describe_*' pattern in AWS services typically queries existing information without modification. Description is empty, which lowers confidence slightly.

Questions about describe_severity_levels

What does the describe_severity_levels tool do? +

describe_severity_levels. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on describe_severity_levels? +

Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for describe_severity_levels: 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 describe_severity_levels? +

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

Can I rate-limit describe_severity_levels? +

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

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

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.