Retrieve system patterns
AI agents call get_system_patterns 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.
The verb 'Retrieve' and the absence of any side effects, state changes, or code execution indicate this is a simple data query operation. It fetches existing system patterns from the knowledge base without altering state, deleting data, or executing external operations. This fits the Read category with low severity since pattern retrieval poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_system_patterns' and description 'Retrieve system patterns' indicate a read-only retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
Retrieve system patterns. 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 get_system_patterns: 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.
get_system_patterns 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 get_system_patterns 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 get_system_patterns. 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.
get_system_patterns 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 →