Store an SDOF plan with metadata
AI agents use store_sdof_plan 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 creates or persists data (an SDOF plan with metadata) reversibly within the knowledge base. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or retrieve data (Read). Write is the appropriate category.
From the tool's definition Tool name and description indicate creating or storing a plan: 'Store an SDOF plan with metadata'. The verb 'store' implies creating or modifying data in persistent memory.
Attacks that exploit this kind of access
Store an SDOF plan with metadata. 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 store_sdof_plan: 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.
store_sdof_plan 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 store_sdof_plan 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 store_sdof_plan. 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.
store_sdof_plan 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 →