Create a junction table for many-to-many relationships
AI agents use quickbase_create_junction_table 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 database table, which is a reversible write operation. While schema changes can have significant impact on a database, creating a junction table does not delete data or execute arbitrary code. It modifies database structure but can be undone by dropping the table.
From the tool's definition Tool name contains 'create' and description states 'Create a junction table', indicating data structure creation that modifies the database schema by adding a new table for relationship management.
Attacks that exploit this kind of access
Create a junction table for many-to-many relationships. 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_junction_table: 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_junction_table 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_junction_table 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_junction_table. 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_junction_table 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 →