AI agents call get_protocol_contracts 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 retrieves and displays information about contracts associated with a protocol. It has no side effects, does not modify data, execute code, delete data, or move funds. It is a straightforward data lookup operation consistent with other sibling tools like 'get_protocol', 'get_protocols', and 'identify_application' which are all Read operations on blockchain metadata.
From the tool's definition Tool name 'get_protocol_contracts' and description 'List all known application contracts for a Voi protocol' indicate a retrieval operation. The verb 'list' is a classic Read operation that queries existing data without modification.
Attacks that exploit this kind of access
List all known application contracts for a Voi protocol. 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_protocol_contracts: 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_protocol_contracts 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_protocol_contracts 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_protocol_contracts. 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_protocol_contracts 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 →