add_image_container_locations · RSpace MCP Server MCP

WHAT IT DOES

What add_image_container_locations does on RSpace MCP Server

AI agents use add_image_container_locations 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.

WHY IT NEEDS A POLICY

Why add_image_container_locations needs a policy

The tool creates or adds new markers to an image container, which is a modification operation. This fits the Write category: data is being created/added rather than deleted or executed as arbitrary code. The severity is medium because modifying research data could affect data integrity or experimental records, but the operation is reversible (markers can be removed or corrected).

From the tool's definition Tool description states 'Adds new marker locations to an existing image container' — this is a create/add operation that modifies data (image container locations) reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_image_container_locations Rate-limited

add_image_container_locations 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": {
    "add_image_container_locations": {
      "limits": [
        {
          "counter": "add_image_container_locations_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 RSpace MCP Server, so you can run agents against it safely.

FAQ

Questions about add_image_container_locations

What does the add_image_container_locations tool do? +

Adds new marker locations to an existing image container. 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.

How do I enforce a policy on add_image_container_locations? +

Register the RSpace MCP Server MCP server in PolicyLayer and add a rule for add_image_container_locations: 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.

What risk level is add_image_container_locations? +

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

Can I rate-limit add_image_container_locations? +

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

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

add_image_container_locations 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.