search_within_results

Refine previous search results with an additional query. Useful for progressive search refinement: first search broadly (e.g.,

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

What search_within_results does on TDZ C64 Knowledge

AI agents call search_within_results 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_within_results needs a policy

This tool retrieves and filters existing search results without modifying, deleting, or executing any operations. It performs a secondary query against cached or in-memory search results, which is a non-destructive read operation with no side effects or capability to alter data. The low severity reflects minimal blast radius—a misused search refinement cannot cause harm beyond returning incorrect information.

From the tool's definition Tool name is 'search_within_results' and description explicitly states it 'Refine previous search results with an additional query' - a read-only refinement operation on already-fetched search results.

Questions about search_within_results

What does the search_within_results tool do? +

Refine previous search results with an additional query. Useful for progressive search refinement: first search broadly (e.g.,. 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_within_results? +

Register the TDZ C64 Knowledge MCP server in PolicyLayer and add a rule for search_within_results: 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_within_results? +

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

Can I rate-limit search_within_results? +

Yes. Add a rate_limit block to the search_within_results 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_within_results completely? +

Set action: deny in the PolicyLayer policy for search_within_results. 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_within_results? +

search_within_results 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.