AI agents call build_export_url to retrieve information from Spline without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool constructs/generates a URL from a scene ID. It is a read/compute operation with no side effects — it builds a URL string but does not fetch, modify, or delete any data. Severity is low as misuse only produces a URL.
From the tool's definition Build Spline export URL from scene ID
Attacks that exploit this kind of access
Build Spline export URL from scene ID. It is categorised as a Read tool in the Spline MCP Server, which means it retrieves data without modifying state.
Register the Spline MCP server in PolicyLayer and add a rule for build_export_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 Spline. Nothing to install.
build_export_url is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the build_export_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 build_export_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.
build_export_url is provided by the Spline MCP server (lesleslie/spline-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 →