List configured instrument slots
AI agents call list_slots to retrieve information from Moku MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates existing instrument slot configurations from a Moku device. The verb 'list' and absence of any modification language (create, delete, update, deploy) confirm it is a read-only operation. Even in the context of device control, listing current state poses minimal risk—it gathers information without altering device state or triggering operations.
From the tool's definition Tool name 'list_slots' and description 'List configured instrument slots' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List configured instrument slots. It is categorised as a Read tool in the Moku MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Moku MCP Server MCP server in PolicyLayer and add a rule for list_slots: 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 Moku MCP Server. Nothing to install.
list_slots 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 list_slots 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 list_slots. 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.
list_slots is provided by the Moku MCP Server MCP server (sealablab/moku-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 →