search

THE RISK

Low Risk

Why search needs a policy

This tool performs read-only queries against a public issue tracking and version control system. It retrieves and searches existing data without creating, modifying, deleting, or executing any operations. The worst-case misuse scenario is excessive queries or information leakage about WordPress development, both low-severity risks.

From the tool's definition Tool named 'search' that queries WordPress Trac for tickets, changesets, and timeline activity. Description indicates data retrieval operations ('Search WordPress Trac for tickets, changesets, and timeline activity') with no mention of modification, deletion,…

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

POLICY

How to control search

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search": {}
  }
}

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

Create a free account and register WordPress Trac MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More WordPress Trac MCP Server tools

Read fetch Retrieve detailed information about a specific WordPress Trac item by its ID. Read getChangeset Get information about a specific WordPress code changeset/commit including commit message, Read getTicket Get detailed information about a specific WordPress Trac ticket including description, com Read getTimeline Get recent activity from WordPress Trac timeline including recent tickets, commits, and ot Read getTracInfo Get WordPress Trac metadata like components, milestones, priorities, and severities. Read searchTickets Search for WordPress Trac tickets by keyword or filter expression. Returns ticket summarie

All 7 WordPress Trac MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search

What does the search tool do? +

Search WordPress Trac for tickets, changesets, and timeline activity. Query Types: - Ticket searches: Use keywords like. It is categorised as a Read tool in the WordPress Trac MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search? +

Register the WordPress Trac MCP Server MCP server in PolicyLayer and add a rule for 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 WordPress Trac MCP Server. Nothing to install.

What risk level is search? +

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

Can I rate-limit search? +

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

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

search is provided by the WordPress Trac MCP Server MCP server (jameswlepage/trac-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every WordPress Trac MCP Server tool call.

Start from WordPress Trac MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →