Low Risk

docs.search

Search the Temporal documentation corpus for relevant information.

How to control docs.search ↓

What docs.search does on Temporal

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

Low Risk

Why docs.search needs a policy

This tool retrieves and searches documentation without modifying, executing, or deleting anything. It has no side effects beyond returning search results. The blast radius of misuse is minimal—an agent could waste resources or retrieve inappropriate information, but cannot alter state or trigger external operations.

From the tool's definition Tool name 'docs.search' and description 'Search the Temporal documentation corpus for relevant information' indicate a query operation over static documentation.

Documented attack patterns abuse exactly the kind of access docs.search gives an agent:

How to control docs.search

PolicyLayer is an MCP gateway — it sits between your AI agents and Temporal, and nothing reaches the server without passing your rules. This is the rule we recommend for docs.search:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "docs.search": {}
  }
}

docs.search is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Temporal — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about docs.search

What does the docs.search tool do? +

Search the Temporal documentation corpus for relevant information. It is categorised as a Read tool in the Temporal MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on docs.search? +

Register the Temporal MCP server in PolicyLayer and add a rule for docs.search: 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 Temporal. Nothing to install.

What risk level is docs.search? +

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

Can I rate-limit docs.search? +

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

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

docs.search is provided by the Temporal MCP server (stevekinney/temporal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Temporal tool call.

Start from Temporal, 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.

28 Temporal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.