Set the 3DSpace URL that will be used for all API calls
AI agents use set_3dspace_url to create or update resources in 3dspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 3dspace environment.
This tool creates or modifies configuration data (the 3DSpace URL endpoint) in a reversible manner. While not directly destructive, it could cause significant disruption if set incorrectly—redirecting all API calls to a wrong endpoint, potentially to a malicious URL (if an attacker hijacks the agent), or causing legitimate operations to fail. This makes it Write-category with medium severity.
From the tool's definition Tool name indicates 'set' operation which modifies configuration state. Description states it 'will be used for all API calls', meaning it persistently changes a setting that affects subsequent operations.
Documented attack patterns abuse exactly the kind of access set_3dspace_url gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 3dspace, and nothing reaches the server without passing your rules. This is the rule we recommend for set_3dspace_url:
{
"version": "1",
"default": "deny",
"tools": {
"set_3dspace_url": {
"limits": [
{
"counter": "set_3dspace_url_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_3dspace_url 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.
Free to start. No card required.
Set the 3DSpace URL that will be used for all API calls. It is categorised as a Write tool in the 3dspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 3dspace MCP server in PolicyLayer and add a rule for set_3dspace_url: 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 3dspace. Nothing to install.
set_3dspace_url 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 set_3dspace_url 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 set_3dspace_url. 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.
set_3dspace_url is provided by the 3dspace MCP server (pgupta1795/3dspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 3dspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 3dspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.