tk-list-entities
List all available OData entity sets in the Tweedekamer Gegevensmagazijn.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/tk-list-entities.md
What tk-list-entities does on Meta Data Mcp
AI agents call tk-list-entities 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-list-entities is rated Low
This tool queries and retrieves metadata about available OData entity sets from the Tweedekamer Gegevensmagazijn (Dutch parliament data warehouse). It performs a non-destructive retrieval operation with no capacity to modify, delete, or execute external code. The blast radius of misuse is minimal—an AI agent can only learn what entities exist, not access or alter any data.
From the tool's definition Tool name 'tk-list-entities' and description 'List all available OData entity sets' indicate a retrieval/query operation with no modification or side effects. The verb 'list' is explicitly a read operation.
Attacks that exploit this kind of access
The rule that runs tk-list-entities 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-list-entities, this is the rule to start with:
tk-list-entities 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-list-entities call is checked against it from then on.
Questions about tk-list-entities
List all available OData entity sets in the Tweedekamer Gegevensmagazijn. 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-list-entities: 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-list-entities 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-list-entities 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-list-entities. 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-list-entities 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