This record as markdown: /tools/7gugu-whistle-mcp/getvaluelist.md
What getValueList does on Whistle
AI agents call getValueList to retrieve information from Whistle without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getValueList is rated Low
This is a read-only operation that queries and retrieves metadata about values without modifying any state. The description explicitly constrains the response to index and name fields, confirming its purpose is data retrieval with no side effects. No creation, modification, deletion, code execution, or financial impact is possible.
From the tool's definition Tool name 'getValueList' and description indicate it retrieves a list of values with only index and name fields, explicitly avoiding returning data fields to prevent large data volumes.
Attacks that exploit this kind of access
The rule that runs getValueList 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 getValueList, this is the rule to start with:
getValueList is read-only, so it stays allowed. 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 getValueList call is checked against it from then on.
Questions about getValueList
获取值列表（仅包含 index 和 name，不包含 data 字段，避免数据量过大）. It is categorised as a Read tool in the Whistle MCP Server, which means it retrieves data without modifying state.
Register the Whistle MCP server in PolicyLayer and add a rule for getValueList: 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.
getValueList is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getValueList 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 getValueList. 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.
getValueList 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