AI agents call identify_application 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 queries a registry or semantic layer to retrieve information about a Voi application. It performs a lookup operation with no side effects, matching the 'Read' category definition (retrieves or queries data; no side effects). The severity is low because misuse by an AI agent would only expose existing public blockchain ecosystem data without enabling harm to systems or assets.
From the tool's definition Tool 'identify_application' retrieves application metadata (protocol, role, type, description) by ID from a semantic layer over blockchain data.
Attacks that exploit this kind of access
Identify a Voi application by ID — returns protocol, role, type, and description if known. 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 identify_application: 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.
identify_application 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 identify_application 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 identify_application. 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.
identify_application 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 →