Retrieves detailed information about a specific parliamentary committee, including its members, recent activities, and description. This provides deeper insight into the committee
AI agents call get_committee_details 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 parliamentary committee information (members, activities, description) with no side effects, modifications, deletions, or execution of external operations. It is a straightforward data retrieval operation fitting the 'Read' category. Severity is low as exposure of public parliamentary committee information poses minimal risk.
From the tool's definition Tool name 'get_committee_details' and description 'Retrieves detailed information about a specific parliamentary committee, including its members, recent activities, and description' clearly indicate a read-only operation that queries and returns data without…
Documented attack patterns abuse exactly the kind of access get_committee_details 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_committee_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_committee_details": {}
}
}get_committee_details 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 detailed information about a specific parliamentary committee, including its members, recent activities, and description. This provides deeper insight into the committee. 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_committee_details: 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_committee_details 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_committee_details 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_committee_details. 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_committee_details 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.