This record as markdown: /tools/7gugu-whistle-mcp/createvalue.md
What createValue does on Whistle
AI agents use createValue 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 createValue is rated Medium
This tool creates new data within the Whistle proxy system (values used in proxy rules and groups). It is reversible via deleteValue, making it Write rather than Destructive. The severity is medium because misuse could create problematic proxy configurations affecting network traffic monitoring/interception, but the impact is limited to the local Whistle proxy and is reversible.
From the tool's definition Tool name 'createValue' and description '创建新的值' (create new value) indicate data creation. In the context of Whistle proxy management, this creates new values for proxy rules/configuration.
Attacks that exploit this kind of access
The rule that runs createValue 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 createValue, this is the rule to start with:
createValue 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 createValue call is checked against it from then on.
Questions about createValue
创建新的值. 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 createValue: 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.
createValue 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 createValue 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 createValue. 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.
createValue 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