get_component
AI agents call get_component 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.
In the absence of descriptive content, the tool name 'get_component' strongly suggests a retrieval operation that queries component data without side effects. AWS IoT SiteWise components are typically accessed for inspection or monitoring. The 'get_' prefix is a standard convention for Read operations. Confidence is moderate due to the lack of explicit documentation.
From the tool's definition Tool name 'get_component' follows the Read pattern (get is a standard retrieval operation). Description is empty, limiting evidence, but the sibling tools on this AWS IoT SiteWise MCP server include many Read-like operations (aggregate, analyze_*) and Write…
Attacks that exploit this kind of access
get_component. 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_component: 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_component 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_component 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_component. 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_component 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.