json_set
AI agents use json_set to create or update resources in AWS IoT SiteWise MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS IoT SiteWise MCP Server environment.
The name 'json_set' implies a write operation that creates or modifies JSON data reversibly. Without a description, confidence is reduced, but the naming pattern aligns with write operations rather than reads, destructive actions, or code execution. In an AWS IoT SiteWise context, such operations would typically modify configuration or metadata rather than delete data or execute arbitrary code.
From the tool's definition Tool name 'json_set' indicates modification of JSON data structures; empty description limits confidence but naming convention suggests creating or updating a value within a JSON object or configuration.
Attacks that exploit this kind of access
json_set. It is categorised as a Write tool in the AWS IoT SiteWise MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS IoT SiteWise MCP Server MCP server in PolicyLayer and add a rule for json_set: 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.
json_set is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the json_set 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 json_set. 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.
json_set 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.