add_extra_fields_to_item
AI agents use add_extra_fields_to_item 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.
The verb 'add' combined with the action of extending an item with new fields indicates a reversible data modification operation (Write category). Severity is medium because modifying item metadata in a research management system could affect data integrity or downstream processes, but is not destructive or financial.
From the tool's definition Tool name 'add_extra_fields_to_item' indicates modification of an item's properties by adding fields. Description is empty, so classification relies on the name and context of sibling tools which perform create/modify operations on RSpace research data.
Attacks that exploit this kind of access
add_extra_fields_to_item. 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 add_extra_fields_to_item: 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.
add_extra_fields_to_item 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 add_extra_fields_to_item 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 add_extra_fields_to_item. 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.
add_extra_fields_to_item 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 →