Gets detailed information about a keyspace - args: keyspace
AI agents call describeKeyspace 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.
The verb 'describe' is a standard read operation that retrieves metadata about a resource without altering state. The tool fetches information about a keyspace using a single argument. No data is created, modified, deleted, or executed. This is a straightforward informational query with minimal blast radius if misused by an agent.
From the tool's definition Tool name 'describeKeyspace' and description 'Gets detailed information about a keyspace' indicate a query/retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Gets detailed information about a keyspace - args: keyspace. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for describeKeyspace: 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.
describeKeyspace is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describeKeyspace 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.
Set action: deny in the PolicyLayer policy for describeKeyspace. 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.
describeKeyspace 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.