Force a DSPy optimization run if available and not already running.
AI agents invoke force_dspy_optimization to trigger actions in Graph Rag Obsidian. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an optimization process (DSPy is a framework for optimizing LLM pipelines). 'Force' and 'run' indicate it executes an external operation. The effects depend on the current state of the system and available data, making it Execute. It's not purely destructive or financial, but it does trigger a potentially expensive or side-effectful computation process.
From the tool's definition Force a DSPy optimization run if available and not already running
Attacks that exploit this kind of access
Force a DSPy optimization run if available and not already running. It is categorised as a Execute tool in the Graph Rag Obsidian MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Graph Rag Obsidian MCP server in PolicyLayer and add a rule for force_dspy_optimization: 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 Graph Rag Obsidian. Nothing to install.
force_dspy_optimization is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the force_dspy_optimization 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 force_dspy_optimization. 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.
force_dspy_optimization is provided by the Graph Rag Obsidian MCP server (nickshffer/graph-rag-mcp-server). 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 →