列出当前可用的所有仪器命令。
AI agents call get_available_tools to retrieve information from Instrument MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation—enumerating available commands. It has no side effects, does not execute commands, does not modify data, and does not move money or delete anything. Even in the context of test instrument control, simply listing available tools is passive discovery with minimal security impact. Misuse would not cause physical harm or data loss.
From the tool's definition Tool name 'get_available_tools' and function to '列出当前可用的所有仪器命令' (list all available instrument commands) indicate a query/list operation that retrieves information about available commands without modifying state or executing operations.
Attacks that exploit this kind of access
列出当前可用的所有仪器命令。. It is categorised as a Read tool in the Instrument MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Instrument MCP Server MCP server in PolicyLayer and add a rule for get_available_tools: 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 Instrument MCP Server. Nothing to install.
get_available_tools 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 get_available_tools 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 get_available_tools. 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.
get_available_tools is provided by the Instrument MCP Server MCP server (zeng-andrew/instrument-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →