Validate that a global foundation applies in the current project. Increases confidence and adds current project to validated_in list. Strong signal for keeping foundation at global scope. Use when you observe a global foundation being correct in a new project context.
AI agents use validate_foundation to create or update resources in Decision OS MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Decision OS MCP environment.
The tool modifies a foundation record by incrementing a confidence value and adding an entry to a list. These are reversible data updates (Write category). The blast radius is low since it only augments metadata on a knowledge-base entry rather than deleting or executing code.
From the tool's definition 'Increases confidence and adds current project to validated_in list' — modifies existing foundation record by updating confidence score and appending to validated_in list
Attacks that exploit this kind of access
Validate that a global foundation applies in the current project. Increases confidence and adds current project to validated_in list. Strong signal for keeping foundation at global scope. Use when you observe a global foundation being correct in a new project context. It is categorised as a Write tool in the Decision OS MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Decision OS MCP server in PolicyLayer and add a rule for validate_foundation: 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 Decision OS MCP. Nothing to install.
validate_foundation 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 validate_foundation 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 validate_foundation. 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.
validate_foundation is provided by the Decision OS MCP server (marianstefi20/decision-os-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 →