Performs a semantic search across ConPort data.
AI agents call semantic_search_conport 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 retrieves and queries data (semantic search) without side effects. It does not create, modify, delete, or execute operations. The search operation is read-only, returning results without altering the underlying data. This is a standard Read category operation with low severity due to its passive, non-destructive nature.
From the tool's definition Tool name 'semantic_search_conport' and description 'Performs a semantic search across ConPort data' indicate a query/search operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
Performs a semantic search across ConPort data. 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 semantic_search_conport: 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.
semantic_search_conport 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 semantic_search_conport 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 semantic_search_conport. 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.
semantic_search_conport 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 →