This record as markdown: /tools/7gugu-whistle-mcp/updatevalue.md
What updateValue does on Whistle
AI agents use updateValue to create or update resources in Whistle, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whistle environment.
Why updateValue is rated Medium
This tool creates or modifies configuration data reversibly within the Whistle proxy server. It does not delete data (which would be Destructive), execute arbitrary commands (Execute), or involve financial transactions. Users can revert changes by updating values again, making it a Write operation.
From the tool's definition Tool name is 'updateValue' and description states '更新值内容' (update value content). This modifies existing data within the Whistle proxy configuration by updating stored values.
Attacks that exploit this kind of access
The rule that runs updateValue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Whistle, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For updateValue, this is the rule to start with:
updateValue stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Whistle, apply this rule, and every updateValue call is checked against it from then on.
Questions about updateValue
更新值内容. It is categorised as a Write tool in the Whistle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whistle MCP server in PolicyLayer and add a rule for updateValue: 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 Whistle. Nothing to install.
updateValue 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 updateValue 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 updateValue. 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.
updateValue is provided by the Whistle MCP server (7gugu/whistle-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Whistle, and thousands of servers like it.
This server
Across the catalogue