get_config_check_operation
AI agents call get_config_check_operation 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 'get' strongly suggests this is a read operation that retrieves information about a configuration check operation. Without a description, confidence is moderate, but the naming convention points to a non-mutative query. No evidence of side effects, deletion, execution, or financial impact. Classification as Read is appropriate with lowered confidence due to missing descriptive details.
From the tool's definition Tool name 'get_config_check_operation' contains 'get', which indicates a retrieval operation. Description is empty, limiting direct evidence.
Attacks that exploit this kind of access
get_config_check_operation. 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_config_check_operation: 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_config_check_operation 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_config_check_operation 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_config_check_operation. 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_config_check_operation 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.