Create a parent-child relationship between tables
AI agents use quickbase_create_relationship to create or update resources in QuickBase MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuickBase MCP Server environment.
This tool creates a new relationship between tables, which is a reversible modification to the database schema. It is Write-category because it creates/modifies data structures (relationships) without permanently destroying data or executing arbitrary code.
From the tool's definition Tool name 'quickbase_create_relationship' and description 'Create a parent-child relationship between tables' indicate a data modification operation that establishes a new schema relationship.
Attacks that exploit this kind of access
Create a parent-child relationship between tables. It is categorised as a Write tool in the QuickBase MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the QuickBase MCP Server MCP server in PolicyLayer and add a rule for quickbase_create_relationship: 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 QuickBase MCP Server. Nothing to install.
quickbase_create_relationship 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 quickbase_create_relationship 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 quickbase_create_relationship. 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.
quickbase_create_relationship is provided by the QuickBase MCP Server MCP server (lawrencecirillo/quickbase-mcp-server). 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 →