Searches for all occurrences of a person
AI agents call find_person_in_document to retrieve information from OpenTK Model Context Protocol Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that searches for and returns information about person mentions within documents. It queries existing data from the Dutch parliamentary system without creating, modifying, deleting, or executing any operations.
From the tool's definition Tool name 'find_person_in_document' and description 'Searches for all occurrences of a person' indicate a search/query operation that retrieves data without modification or side effects.
Documented attack patterns abuse exactly the kind of access find_person_in_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenTK Model Context Protocol Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_person_in_document:
{
"version": "1",
"default": "deny",
"tools": {
"find_person_in_document": {}
}
} find_person_in_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Searches for all occurrences of a person. It is categorised as a Read tool in the OpenTK Model Context Protocol Server MCP Server, which means it retrieves data without modifying state.
Register the OpenTK Model Context Protocol Server MCP server in PolicyLayer and add a rule for find_person_in_document: 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 OpenTK Model Context Protocol Server. Nothing to install.
find_person_in_document 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_person_in_document 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_person_in_document. 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_person_in_document is provided by the OpenTK Model Context Protocol Server MCP server (r-huijts/opentk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OpenTK Model Context Protocol Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 OpenTK Model Context Protocol Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.