register_entity · Sourcesage MCP: Risk & Policy

WHAT IT DOES

What register_entity does on Sourcesage

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

WHY IT NEEDS A POLICY

Why register_entity needs a policy

This tool creates or adds new entries to a knowledge graph, which is a reversible write operation. It does not execute arbitrary code, delete data, or affect external systems.

From the tool's definition Tool description: 'Register a code entity in the knowledge graph'. The verb 'register' indicates creation/modification of data in a persistent knowledge structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_entity Rate-limited

register_entity 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_entity": {
      "limits": [
        {
          "counter": "register_entity_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 Sourcesage, so you can run agents against it safely.

FAQ

Questions about register_entity

What does the register_entity tool do? +

Register a code entity in the knowledge graph. It is categorised as a Write tool in the Sourcesage 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_entity? +

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

What risk level is register_entity? +

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

Can I rate-limit register_entity? +

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

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

register_entity is provided by the Sourcesage MCP server (mcpflow/sourcesage). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.