ecs_resource_management
AI agents call ecs_resource_management as a supporting operation in AWS IoT SiteWise MCP Server workflows.
With no description available, it's impossible to determine the specific operations this tool performs. The name suggests managing ECS resources which could span multiple severity categories. Defaulting to 'Other' with low confidence due to lack of information, though the potential blast radius is medium given ECS resource management could affect running infrastructure.
From the tool's definition Tool description is empty and uninformative; tool name 'ecs_resource_management' suggests ECS resource management but exact operations (read, write, execute, destructive) are unclear.
Attacks that exploit this kind of access
ecs_resource_management. It is categorised as a Other tool in the AWS IoT SiteWise MCP Server MCP Server, which means it performs auxiliary operations.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for ecs_resource_management: 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.
ecs_resource_management is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ecs_resource_management 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 ecs_resource_management. 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.
ecs_resource_management 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.