This record as markdown: /tools/io-github-portel-dev-ncp/register-service.md
What register_service does on Ncp
AI agents use register_service to create or update resources in Ncp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ncp environment.
Why register_service is rated Medium
Registering a service in Consul creates new service discovery metadata and can modify existing service configurations. This is a reversible write operation that affects service orchestration and discoverability. It could be misused to register malicious services or redirect traffic, but is not destructive (entries can be deregistered) or financially harmful.
From the tool's definition Tool name 'register_service' combined with description 'Register service with Consul' indicates creation or modification of service registry entries in Consul.
Attacks that exploit this kind of access
The rule that runs register_service safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ncp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For register_service, this is the rule to start with:
register_service 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ncp, apply this rule, and every register_service call is checked against it from then on.
Questions about register_service
Register service with Consul. It is categorised as a Write tool in the Ncp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ncp MCP server in PolicyLayer and add a rule for register_service: 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 Ncp. Nothing to install.
register_service 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 register_service 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 register_service. 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.
register_service is provided by the Ncp MCP server (@portel/ncp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ncp, and thousands of servers like it.
This server
Across the catalogue