Get product context
AI agents call get_product_context 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 or queries product context data without modifying, deleting, or executing operations. It falls squarely into the Read category—a safe data retrieval operation with minimal blast radius if misused by an AI agent. The presence of sibling destructive tools (delete_*) on the server further confirms this is distinct as a non-destructive read operation.
From the tool's definition Tool name 'get_product_context' and description 'Get product context' indicate a retrieval operation. The verb 'Get' is characteristic of read-only data access. No mutation, deletion, or execution keywords are present.
Attacks that exploit this kind of access
Get product context. 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_product_context: 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_product_context 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_product_context 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_product_context. 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_product_context 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 →