tk-query
Query a Tweedekamer entity set using OData v4 parameters.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/tk-query.md
What tk-query does on Meta Data Mcp
AI agents call tk-query to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why tk-query is rated Low
This tool retrieves data from the Tweedekamer (Dutch parliament) open data API using OData query parameters. OData is a standardized protocol for read access to data sources. There is no indication of write, delete, execute, or financial operations. The tool fits squarely in the Read category with low severity since it accesses public government data without side effects.
From the tool's definition Tool name 'tk-query' and description 'Query a Tweedekamer entity set using OData v4 parameters' indicate a data retrieval operation.
Attacks that exploit this kind of access
The rule that runs tk-query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tk-query, this is the rule to start with:
tk-query is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every tk-query call is checked against it from then on.
Questions about tk-query
Query a Tweedekamer entity set using OData v4 parameters. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for tk-query: 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 Meta Data Mcp. Nothing to install.
tk-query 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 tk-query 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 tk-query. 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.
tk-query is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue