Retrieves a list of all parliamentary committees with their IDs, names, and URLs. The response is a JSON array where each entry represents a committee with its unique identifier and name. Committees are specialized groups of MPs that focus on specific domains like defense, healthcare, or finance....
AI agents call get_committees 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 performs a simple retrieval of public parliamentary committee information. It does not modify, delete, or execute any operations—it only queries and returns static reference data. The data returned (committee names, IDs, and URLs) is public parliamentary metadata with no sensitive information exposure or operational risk.
From the tool's definition Tool description explicitly states it 'Retrieves a list of all parliamentary committees' and 'takes no parameters as it returns all active committees.' The verb 'retrieves' combined with read-only data retrieval (committee metadata: IDs, names, URLs)…
Documented attack patterns abuse exactly the kind of access get_committees 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 get_committees:
{
"version": "1",
"default": "deny",
"tools": {
"get_committees": {}
}
}get_committees 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.
Retrieves a list of all parliamentary committees with their IDs, names, and URLs. The response is a JSON array where each entry represents a committee with its unique identifier and name. Committees are specialized groups of MPs that focus on specific domains like defense, healthcare, or finance. This tool takes no parameters as it returns all active committees. 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 get_committees: 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.
get_committees 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 get_committees 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 get_committees. 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.
get_committees 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.