Hides a form from document creation interface
AI agents use unpublish_form 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.
Unpublishing a form changes its visibility/state in the system but is likely reversible (forms can typically be re-published). This is a state modification rather than a deletion, so it falls under Write rather than Destructive. The blast radius is medium as it could disrupt users from creating documents using that form.
From the tool's definition Hides a form from document creation interface
Attacks that exploit this kind of access
Hides a form from document creation interface. 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 unpublish_form: 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.
unpublish_form 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 unpublish_form 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 unpublish_form. 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.
unpublish_form 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 →