This record as markdown: /tools/nasbridge/replication-get.md
What replication_get does on Nasbridge
AI agents call replication_get to retrieve information from Nasbridge without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why replication_get is rated Low
This is a straightforward read operation that retrieves replication task information by identifier. It queries system state without creating, modifying, deleting, or executing any operations. The 'Get' verb and read-only nature clearly place it in the Read category with low severity, as misuse would only expose existing data rather than cause system changes.
From the tool's definition Tool name 'replication_get' and description 'Get a replication task by ID' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs replication_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For replication_get, this is the rule to start with:
replication_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every replication_get call is checked against it from then on.
Questions about replication_get
Get a replication task by ID. It is categorised as a Read tool in the Nasbridge MCP Server, which means it retrieves data without modifying state.
Register the Nasbridge MCP server in PolicyLayer and add a rule for replication_get: 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 Nasbridge. Nothing to install.
replication_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the replication_get 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 replication_get. 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.
replication_get is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
This server
Across the catalogue