Update product context
AI agents use update_product_context to create or update resources in SDOF Knowledge Base — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SDOF Knowledge Base environment.
This tool modifies product context data, which is a write operation. The 'update' action is reversible (can be updated again or reverted), so it does not qualify as Destructive. The effect is bounded to product context state within the knowledge base, not financial transactions or arbitrary code execution.
From the tool's definition Tool name 'update_product_context' and description 'Update product context' indicate modification of data. The verb 'update' directly maps to the Write category (creates or modifies data reversibly).
Attacks that exploit this kind of access
Update product context. It is categorised as a Write tool in the SDOF Knowledge Base MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for update_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.
update_product_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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 →