agent.register · Signomy MCP: Risk & Policy

WHAT IT DOES

What agent.register does on Signomy

AI agents use agent.register to create or update resources in Signomy — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Signomy environment.

WHY IT NEEDS A POLICY

Why agent.register needs a policy

Registration creates new persistent records (agent account) that modify system state reversibly. This is a Write operation rather than Read (retrieves data) or Destructive (irreversible deletion). Severity is medium because unauthorized agent registration could enable subsequent misuse of financial tools (agent.cashout) or abuse of the governed system, but the registration itself is reversible.

From the tool's definition Tool name 'agent.register' indicates account/agent registration, which creates new data in the system. The server description mentions 'Register as an agent' as a core function, confirming this tool creates new records. The sibling tools (agent.cashout, agent.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

agent.register Rate-limited

agent.register 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": {
    "agent.register": {
      "limits": [
        {
          "counter": "agent.register_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 Signomy, so you can run agents against it safely.

FAQ

Questions about agent.register

What does the agent.register tool do? +

agent.register. It is categorised as a Write tool in the Signomy MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on agent.register? +

Register the Signomy MCP server in PolicyLayer and add a rule for agent.register: 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 Signomy. Nothing to install.

What risk level is agent.register? +

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

Can I rate-limit agent.register? +

Yes. Add a rate_limit block to the agent.register 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 agent.register completely? +

Set action: deny in the PolicyLayer policy for agent.register. 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 agent.register? +

agent.register is provided by the Signomy MCP server (sunrisesillneversee/agent-universe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.