AI agents call get_protocols to retrieve information from UluVoiMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward read operation that fetches information about protocols from a registry or database. It has no capability to modify, delete, or execute operations. The 'list' action is explicitly a read operation with no side effects. The semantic layer context confirms it translates existing blockchain data into human-readable format rather than performing actions.
From the tool's definition Tool name 'get_protocols' with description 'List all known Voi ecosystem protocols with type and description' indicates a query operation that retrieves and lists data without modification or side effects.
Attacks that exploit this kind of access
List all known Voi ecosystem protocols with type and description. It is categorised as a Read tool in the UluVoiMCP MCP Server, which means it retrieves data without modifying state.
Register the UluVoi MCP server in PolicyLayer and add a rule for get_protocols: 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 UluVoiMCP. Nothing to install.
get_protocols 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_protocols 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_protocols. 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_protocols is provided by the UluVoi MCP server (maidtoshelly/uluvoimcp). 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 →