Creates an exact copy of an existing sample
AI agents use duplicate_sample to create or update resources in RSpace MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RSpace MCP Server environment.
This tool creates new data (a duplicate sample) in RSpace without deleting or destroying anything, making it a Write operation rather than Read or Destructive. The severity is high because duplicating research samples at scale could lead to data confusion, wasted resources, or experimental errors if misused by an agent, and the RSpace system manages sensitive research data.
From the tool's definition Tool name is 'duplicate_sample' and description states 'Creates an exact copy of an existing sample' - this is a reversible create operation that adds new data to the system.
Attacks that exploit this kind of access
Creates an exact copy of an existing sample. It is categorised as a Write tool in the RSpace MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for duplicate_sample: 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 RSpace MCP Server. Nothing to install.
duplicate_sample 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 duplicate_sample 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 duplicate_sample. 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.
duplicate_sample is provided by the RSpace MCP Server MCP server (rspace-os/rspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →