get_identity_guide
AI agents call get_identity_guide 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 name 'get_identity_guide' most likely retrieves or fetches identity-related documentation or guidance, which would be a Read operation with no side effects. However, the empty description prevents full certainty of the tool's actual behavior. If this tool were to instead configure or modify identity settings, it would be classified differently.
From the tool's definition Tool name 'get_identity_guide' suggests retrieval of guidance or reference documentation related to identity concepts; the verb 'get' typically indicates a query operation. Description is empty, reducing confidence.
Attacks that exploit this kind of access
get_identity_guide. 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 get_identity_guide: 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.
get_identity_guide 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 get_identity_guide 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 get_identity_guide. 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.
get_identity_guide 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.