apply_yaml
AI agents call apply_yaml as a supporting operation in AWS IoT SiteWise MCP Server workflows.
The tool name 'apply_yaml' suggests it may write or apply configuration via YAML, potentially modifying AWS IoT SiteWise resources. However, with no description available, the exact behavior is unknown. YAML application could range from read-only validation to destructive configuration changes.
From the tool's definition Tool name is 'apply_yaml' but description is empty or uninformative.
Attacks that exploit this kind of access
apply_yaml. 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 apply_yaml: 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.
apply_yaml 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 apply_yaml 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 apply_yaml. 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.
apply_yaml 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.