Find entities by property and value
AI agents call find_by_property to retrieve information from MCP Wikidata Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool searches and retrieves entities based on specified property-value pairs from Wikidata's knowledge graph. It has no side effects—it only queries and returns data. There is no capability to modify, delete, execute commands, or affect financial systems. The blast radius of misuse is minimal since an agent can only learn facts from the Wikidata database, not alter it.
From the tool's definition Tool name 'find_by_property' and description 'Find entities by property and value' indicate a search/retrieval operation. This is a query function that returns data without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Find entities by property and value. It is categorised as a Read tool in the MCP Wikidata Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Wikidata Server MCP server in PolicyLayer and add a rule for find_by_property: 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 Wikidata Server. Nothing to install.
find_by_property 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 find_by_property 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 find_by_property. 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.
find_by_property is provided by the MCP Wikidata Server MCP server (joelgombin/mcp-wikidata). 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 →