AI agents call get_runtime_api_docs 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 retrieves and returns API documentation, which is a query operation that does not modify, execute, or delete any data. It poses minimal security risk as it only exposes information that is typically intended to be public or available to authorized users developing with the Spline runtime API.
From the tool's definition Tool name is 'get_runtime_api_docs' and description states it 'Get[s] documentation for @splinetool/runtime API' — this is a read-only retrieval of reference documentation with no side effects.
Attacks that exploit this kind of access
Get documentation for @splinetool/runtime API. 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 get_runtime_api_docs: 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.
get_runtime_api_docs 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 get_runtime_api_docs 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 get_runtime_api_docs. 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.
get_runtime_api_docs 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 →