AI agents use generate_full_integration to create or update resources in Spline — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Spline environment.
This tool creates or generates integration code/configurations, which falls under the Write category—it produces new artifacts that can be modified or removed. While the description is empty (lowering confidence slightly), the naming pattern and context within a code generation MCP server indicate it creates reversible content rather than executing external operations or destroying data.
From the tool's definition Tool name 'generate_full_integration' combined with sibling tools like 'generate_react_component', 'generate_nextjs_component', and 'generate_snippet' suggests code/integration generation.
Attacks that exploit this kind of access
generate_full_integration. It is categorised as a Write tool in the Spline MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Spline MCP server in PolicyLayer and add a rule for generate_full_integration: 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.
generate_full_integration 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 generate_full_integration 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 generate_full_integration. 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.
generate_full_integration 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 →