Full-text search across parsed module manuals, product pages, and firmware release notes. Use this only when the question is about content that lives in continuous prose rather than in typed fields: - Procedural: calibration sequences, button combos, factory-reset steps, save/load procedures. - D...
Risk signalsAccepts freeform code/query input (query)
Part of the Eurorack server.
Free to start. No card required.
AI agents call search_manual to retrieve information from Eurorack without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_manual only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"search_manual": {}
}
}See the full Eurorack policy for all 17 tools.
These attack patterns abuse exactly the kind of access search_manual gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Full-text search across parsed module manuals, product pages, and firmware release notes. Use this only when the question is about content that lives in continuous prose rather than in typed fields: - Procedural: calibration sequences, button combos, factory-reset steps, save/load procedures. - Diagnostic: LED color meanings, error indicators, troubleshooting trees. - Firmware specifics beyond the short notes on firmware_versions (which only carry the headline change). - Panel walkthroughs and prose explanations that aren't captured as parameters/jacks/zones. Do NOT call this for content already in get_module: a parameter's behavior, a jack's signal type or polarity, a mode's name or description, capability tags, HP, or power draw. Those are typed and authoritative there. Do NOT call this to summarize a module — that's get_module's job. search_manual returns excerpts, not summaries. Returned chunks are source prose, not typed facts. Read them to ground your answer, then paraphrase and point the user to the source to verify (cite-and-point, not reproduce — SKILL.md §8). text is capped (~800 chars); the full passage is at audit_url. Args: - query (string, required): search terms. Plain words are AND'd by default ("calibration LED" matches chunks mentioning both). If the AND match returns 0 rows, the server retries with OR (any-token match) and sets _meta.relaxed_to_or=true on the response — so a long natural-language query like "cascade mode time inner outer delay" still surfaces something useful instead of zeroing out. Best practice is still 2–4 distinctive keywords; the OR fallback is a safety net, not a substitute. Query is tokenized to alphanumeric runs; FTS5 punctuation is stripped. - module_id (string, optional): "<manufacturer>/<module-slug>" — restrict to one module. Strongly recommended when the user has named a module. - source_id (integer, optional): restrict to one source. Use when you already have a source_id from get_source / list_references and want to dig into that specific document. - source_type (string, optional): one of "manual", "product_page", "firmware_notes". Defaults to all. - limit (integer, optional): default 5, max 20. Smaller is usually better — top-3 hits cover most queries. Returns: { "query": string, "matches": [{ "chunk_id": number, "source_id": number, "source_type": string, "source_title": string | null, "module_id": string | null, "heading_path": string, // "Calibration > Tuning Procedure" "snippet": string, // BM25-highlighted excerpt with [matches] in brackets "text": string, // chunk text, capped ~800 chars; paraphrase, don't paste "truncated": boolean, // true if text was trimmed; full passage at audit_url "audit_url": string, // human-readable audit page for the source "rank": number // BM25 score (more negative = better match) }], "total": number, // total matches across the corpus (capped at 200) "_meta": { "kind": "manual_excerpt", "query": <args>, "relaxed_to_or": true // only present when AND returned 0 and OR retry fired } } Examples: - "How do I calibrate Plaits' V/Oct?" → { query: "calibration V/Oct", module_id: "mutable-instruments/plaits" } - "What does the red LED on Marbles mean?" → { query: "red LED", module_id: "mutable-instruments/marbles" } - "How do I reset Pamela's New Workout to defaults?" → { query: "factory reset defaults", module_id: "alm-busy-circuits/pamelas-new-workout" } - "What changed in Plaits firmware 1.2?" → { query: "1.2", module_id: "mutable-instruments/plaits", source_type: "firmware_notes" } Errors: - Returns matches=[] with total=0 if nothing matches. Not an error. - Errors only on malformed input (missing query, invalid limit, unknown source_type).. It is categorised as a Read tool in the Eurorack MCP Server, which means it retrieves data without modifying state.
Register the Eurorack MCP server in PolicyLayer and add a rule for search_manual: 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 Eurorack. Nothing to install.
search_manual 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 search_manual 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 search_manual. 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.
search_manual is provided by the Eurorack MCP server (https://eurorackref.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 Eurorack tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.