Framework confirm karo aur .mcp-config.json save karo
AI agents use confirm_framework to create or update resources in Universal Dev MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Universal Dev MCP environment.
This tool writes or modifies the .mcp-config.json configuration file, which is a reversible data modification. While it could affect system behavior through configuration changes, it does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description indicates it 'confirm[s] Framework' and 'save[s] .mcp-config.json', which are operations that create or modify configuration files. The verb 'save' explicitly denotes a write operation.
Attacks that exploit this kind of access
Framework confirm karo aur .mcp-config.json save karo. It is categorised as a Write tool in the Universal Dev MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Universal Dev MCP server in PolicyLayer and add a rule for confirm_framework: 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 Universal Dev MCP. Nothing to install.
confirm_framework 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 confirm_framework 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 confirm_framework. 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.
confirm_framework is provided by the Universal Dev MCP server (kallusuvaidyam/universal_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 →