DBpedia Lookup search — find entities by label or alias.
AI agents call lookup to retrieve information from Mcp Dbpedia without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The lookup tool searches and retrieves entity information from DBpedia's knowledge graph. It has no side effects, does not modify data, execute code, or perform destructive operations. This is a pure read operation that queries structured data, consistent with a search/lookup pattern. Severity is low because misuse would only surface incorrect or irrelevant information, with no real-world impact.
From the tool's definition Tool is called 'lookup' and described as 'find entities by label or alias' — a search function that retrieves data without modification or execution of arbitrary code.
Attacks that exploit this kind of access
DBpedia Lookup search — find entities by label or alias. It is categorised as a Read tool in the Mcp Dbpedia MCP Server, which means it retrieves data without modifying state.
Register the Mcp Dbpedia MCP server in PolicyLayer and add a rule for lookup: 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 Dbpedia. Nothing to install.
lookup 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 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. 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 is provided by the Mcp Dbpedia MCP server (pipeworx-io/mcp-dbpedia). 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 →