Full-text search across decision fields (summary, rationale, details, tags).
AI agents call search_decisions_fts to retrieve information from SDOF Knowledge Base without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs full-text search (FTS) across indexed decision fields. Search and query operations are read-only retrieval tasks with no side effects, matching the Read category definition. The low severity reflects minimal blast radius—misuse would return unwanted search results but cannot modify state, execute code, or cause financial impact.
From the tool's definition Tool name 'search_decisions_fts' and description explicitly states 'Full-text search across decision fields' - a read-only query operation that retrieves data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Full-text search across decision fields (summary, rationale, details, tags). It is categorised as a Read tool in the SDOF Knowledge Base MCP Server, which means it retrieves data without modifying state.
Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for search_decisions_fts: 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 SDOF Knowledge Base. Nothing to install.
search_decisions_fts 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_decisions_fts 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_decisions_fts. 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_decisions_fts is provided by the SDOF Knowledge Base MCP server (tgf-between-your-legs/sdof-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →