Elevate a project foundation to global scope. Use when a project-specific learning has proven universal. The foundation will be copied to ~/.decision-os with a GF- prefix. Strong signal for elevation: - Foundation has confidence 2+ - Pattern has been validated across multiple implementations - Le...
AI agents use elevate_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.
This tool copies/promotes a project-specific foundation entry to a global scope location (~/.decision-os). It creates a new global record (write operation) but does not delete the original, making it reversible in principle. Misuse could pollute the global knowledge base with incorrect or premature learnings, affecting all future AI assistant decisions system-wide — hence medium severity.
From the tool's definition Elevate a project foundation to global scope... The foundation will be copied to ~/.decision-os with a GF- prefix.
Attacks that exploit this kind of access
Elevate a project foundation to global scope. Use when a project-specific learning has proven universal. The foundation will be copied to ~/.decision-os with a GF- prefix. Strong signal for elevation: - Foundation has confidence 2+ - Pattern has been validated across multiple implementations - Learning applies regardless of tech stack. 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 elevate_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.
elevate_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 elevate_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 elevate_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.
elevate_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 →