AI agents call parse_scene_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.
The tool parses a URL to extract components — this is a read/analysis operation with no side effects, no data modification, and no external operations. It only decomposes a URL string into its constituent parts.
From the tool's definition Parse Spline URL to extract components
Attacks that exploit this kind of access
Parse Spline URL to extract components. 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 parse_scene_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.
parse_scene_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 parse_scene_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 parse_scene_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.
parse_scene_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 →