Semantic search across all blueprint chapters. Returns the most relevant sections with chapter context. Examples: - sophia_blueprint_search("how to add a new agent") → Ch 4 registry pattern - sophia_blueprint_search("memory zone governance") → Ch 5 zone taxonomy - sophia_blueprint_search("reduce ...
Risk signalsAccepts freeform code/query input (query)
Part of the Sophia Architecture server.
Free to start. No card required.
AI agents call sophia_blueprint_search to retrieve information from Sophia Architecture 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 sophia_blueprint_search 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": {
"sophia_blueprint_search": {}
}
}See the full Sophia Architecture policy for all 4 tools.
These attack patterns abuse exactly the kind of access sophia_blueprint_search 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.
Semantic search across all blueprint chapters. Returns the most relevant sections with chapter context. Examples: - sophia_blueprint_search("how to add a new agent") → Ch 4 registry pattern - sophia_blueprint_search("memory zone governance") → Ch 5 zone taxonomy - sophia_blueprint_search("reduce API costs") → Ch 9 model tiering. It is categorised as a Read tool in the Sophia Architecture MCP Server, which means it retrieves data without modifying state.
Register the Sophia Architecture MCP server in PolicyLayer and add a rule for sophia_blueprint_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 Sophia Architecture. Nothing to install.
sophia_blueprint_search 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 sophia_blueprint_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.
Set action: deny in the PolicyLayer policy for sophia_blueprint_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.
sophia_blueprint_search is provided by the Sophia Architecture MCP server (sophia-blueprint/architecture). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Sophia Architecture 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.