List all configured server credentials. Returns server IDs needed for deploy_project.
AI agents call list_servers to retrieve information from Otoinstall without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a retrieval/query operation that reads existing server configuration data. While it exposes server IDs and credentials metadata, it performs no side effects, modifications, or external operations. It is purely informational, making it a Read category tool with low severity since listing available resources does not directly enable harm without combining with other deployment tools.
From the tool's definition Tool 'list_servers' returns data about configured server credentials and server IDs. The description explicitly states it 'Returns server IDs needed for deploy_project' with no indication of modification, deletion, or execution of operations.
Attacks that exploit this kind of access
List all configured server credentials. Returns server IDs needed for deploy_project. It is categorised as a Read tool in the Otoinstall MCP Server, which means it retrieves data without modifying state.
Register the Otoinstall MCP server in PolicyLayer and add a rule for list_servers: 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 Otoinstall. Nothing to install.
list_servers 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_servers 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_servers. 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_servers is provided by the Otoinstall MCP server (otoinstall-mcp-server). 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 →