RSpace MCP Server

63 tools. 39 can modify or destroy data without limits.

6 destructive tools with no built-in limits. Policy required.

Last updated:

39 can modify or destroy data
24 read-only
63 tools total

Community server · catalogue entry verified 29/06/2026

How to control RSpace MCP Server ↓

What RSpace MCP Server exposes to your agents

Read (24) Write / Execute (33) Destructive / Financial (6)
Critical Risk

The most dangerous RSpace MCP Server tools

39 of RSpace MCP Server's 63 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control RSpace MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and RSpace MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations
{
  "delete_container": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "add_extra_fields_to_item": {
    "limits": [
      {
        "counter": "add_extra_fields_to_item_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "downloadFile": {
    "limits": [
      {
        "counter": "downloadfile_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

  1. Create a free account and register RSpace MCP Server — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON RSPACE →

Instant setup, no code required.

All 63 RSpace MCP Server tools

WRITE 33 tools
Write add_extra_fields_to_item add_extra_fields_to_item Write add_image_container_locations Adds new marker locations to an existing image container Write add_note_to_subsample Adds annotations or observations to a specific subsample Write bulk_create_samples bulk_create_samples Write create_document_from_form Creates a structured document using a form template Write create_form create_form Write create_grid_container create_grid_container Write create_image_container create_image_container Write create_list_container create_list_container Write create_sample create_sample Write create_sample_from_template create_sample_from_template Write create_sample_template Creates a reusable template for sample creation Write createNewNotebook Creates a new electronic lab notebook Write createNotebookEntry createNotebookEntry Write duplicate_sample Creates an exact copy of an existing sample Write generate_barcode generate_barcode Write move_items_to_grid_container_by_column Moves items to grid container, filling positions column by column Write move_items_to_grid_container_by_row move_items_to_grid_container_by_row Write move_items_to_image_container move_items_to_image_container Write move_items_to_list_container Moves multiple items to a list-based container Write move_items_to_specific_grid_locations move_items_to_specific_grid_locations Write publish_form Makes a form available for creating documents Write remove_tags_from_document Removes specific tags from a document, leaving other tags intact Write rename_inventory_item Changes the name of any inventory item Write renameDocumentOrNotebookEntry Changes the name/title of a document or notebook entry Write set_item_image Sets or replaces the image for a sample, subsample, or container Write share_form Shares form with user's groups for collaborative use Write split_subsample Divides a subsample into multiple new subsamples Write tagDocumentOrNotebookEntry tagDocumentOrNotebookEntry Write unpublish_form Hides a form from document creation interface Write unshare_form Removes form sharing with groups Write update_document Updates existing RSpace document content and metadata Write uploadAndAttachFile uploadAndAttachFile

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about RSpace MCP Server

Can an AI agent delete data through the RSpace MCP Server MCP server? +

Yes. The RSpace MCP Server server exposes 6 destructive tools including delete_container, delete_form, delete_image_container_locations. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through RSpace MCP Server? +

The RSpace MCP Server server has 33 write tools including add_extra_fields_to_item, add_image_container_locations, add_note_to_subsample. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach RSpace MCP Server.

How many tools does the RSpace MCP Server MCP server expose? +

63 tools across 3 categories: Destructive, Read, Write. 24 are read-only. 39 can modify, create, or delete data.

How do I enforce a policy on RSpace MCP Server? +

Register the RSpace MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every RSpace MCP Server tool call.

Deterministic rules across all 63 RSpace MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

63 RSpace MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.