Performs intelligent pre-analysis of a parliamentary document to determine its relevance WITHOUT loading the full content into your context window. This is a lightweight reconnaissance tool that extracts key information about a document
AI agents call analyze_document_relevance 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 tool retrieves and analyzes metadata/key information from parliamentary documents for querying purposes. It is explicitly designed as a non-intrusive reconnaissance mechanism that does not modify data, execute code, or trigger side effects. The analysis stays within the document domain with no external operations. This is a standard Read operation—data retrieval with no side effects.
From the tool's definition Tool performs 'pre-analysis' and 'extracts key information' without 'loading the full content'. Described as a 'lightweight reconnaissance tool' for determining relevance. No modification, deletion, or execution of external operations mentioned.
Documented attack patterns abuse exactly the kind of access analyze_document_relevance 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 analyze_document_relevance:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_document_relevance": {}
}
}analyze_document_relevance 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.
Performs intelligent pre-analysis of a parliamentary document to determine its relevance WITHOUT loading the full content into your context window. This is a lightweight reconnaissance tool that extracts key information about a document. 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 analyze_document_relevance: 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.
analyze_document_relevance 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 analyze_document_relevance 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 analyze_document_relevance. 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.
analyze_document_relevance 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.