lookup_uri
AI agents call lookup_uri to retrieve information from MCP Server Proto-OKN without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
A URI lookup in a SPARQL/knowledge graph context is fundamentally a retrieval operation that queries data without modifying or deleting anything. Even if it could theoretically support complex operations, the naming convention and peer tools strongly indicate this is a Read operation. The empty description lowers confidence slightly, but the pattern is clear.
From the tool's definition Tool name 'lookup_uri' suggests URI resolution/lookup in a knowledge graph context. Sibling tools like 'get_description', 'get_schema', and 'query' are all read-only query operations. The empty description limits certainty.
Attacks that exploit this kind of access
lookup_uri. It is categorised as a Read tool in the MCP Server Proto-OKN MCP Server, which means it retrieves data without modifying state.
Register the MCP Server Proto-OKN MCP server in PolicyLayer and add a rule for lookup_uri: 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 MCP Server Proto-OKN. Nothing to install.
lookup_uri 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 lookup_uri 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 lookup_uri. 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.
lookup_uri is provided by the MCP Server Proto-OKN MCP server (sbl-sdsc/mcp-proto-okn). 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 →