register_project · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What register_project does on Universal Dev MCP

AI agents use register_project 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.

WHY IT NEEDS A POLICY

Why register_project needs a policy

The tool registers/adds a project to a registry for later switching between projects. This is a write operation that creates or modifies registry entries reversibly. It has minimal blast radius—registering a project incorrectly affects only local development workflow, not production systems or data deletion. No code execution, financial impact, or destructive operations are involved.

From the tool's definition 'add karo' (add) and 'project registry' indicate creating or registering a new project entry in a registry system. This is a reversible data creation operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_project Rate-limited

register_project stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "register_project": {
      "limits": [
        {
          "counter": "register_project_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about register_project

What does the register_project tool do? +

Naya project registry mein add karo taaki baad mein sirf naam se switch ho sake. 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.

How do I enforce a policy on register_project? +

Register the Universal Dev MCP server in PolicyLayer and add a rule for register_project: 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.

What risk level is register_project? +

register_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit register_project? +

Yes. Add a rate_limit block to the register_project 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.

How do I block register_project completely? +

Set action: deny in the PolicyLayer policy for register_project. 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.

What MCP server provides register_project? +

register_project 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.