search_entities

Search for entities across all documents using full-text search. Find all documents mentioning specific hardware, addresses, instructions, people, companies, products, or concepts.

Server TDZ C64 Knowledge michaeltroelsen/tdz-c64-knowledge
Category Read
Risk class Low
Parameters 00 required

What search_entities does on TDZ C64 Knowledge

AI agents call search_entities to retrieve information from TDZ C64 Knowledge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_entities needs a policy

This tool performs full-text search across indexed Commodore 64 documentation to locate and retrieve information about entities (hardware, addresses, instructions, people, companies, products, concepts). It has no side effects, does not create or modify data, and does not execute arbitrary code.

From the tool's definition Tool description explicitly states 'Search for entities' and 'Find all documents mentioning' — these are query/retrieval operations with no modification capability. The verb 'search' and the focus on finding/retrieving information confirm read-only behavior.

Risk signalsBulk/mass operation — affects multiple targets

Questions about search_entities

What does the search_entities tool do? +

Search for entities across all documents using full-text search. Find all documents mentioning specific hardware, addresses, instructions, people, companies, products, or concepts. It is categorised as a Read tool in the TDZ C64 Knowledge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_entities? +

Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for search_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 TDZ C64 Knowledge. Nothing to install.

What risk level is search_entities? +

search_entities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_entities? +

Yes. Add a rate_limit block to the search_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.

How do I block search_entities completely? +

Set action: deny in the PolicyLayer policy for search_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.

What MCP server provides search_entities? +

search_entities is provided by the TDZ C64 Knowledge MCP server (michaeltroelsen/tdz-c64-knowledge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.