assign_mssql_to_package
Assign MSSQL database to hosting package
This record as markdown: /tools/cbrown35-20i-mcp/assign-mssql-to-package.md
What assign_mssql_to_package does on 20i MCP Server
AI agents use assign_mssql_to_package to create or update resources in 20i MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 20i MCP Server environment.
Why assign_mssql_to_package is rated Medium
This tool creates or modifies a configuration relationship between an MSSQL database and a hosting package. This is a reversible Write operation (the assignment can typically be removed or changed). While it affects hosting infrastructure, it does not delete data, execute arbitrary code, or move money.
From the tool's definition Tool description states 'Assign MSSQL database to hosting package' - an assignment operation that modifies the hosting configuration by linking a database resource to a package.
Attacks that exploit this kind of access
The rule that runs assign_mssql_to_package safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 20i MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assign_mssql_to_package, this is the rule to start with:
assign_mssql_to_package stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every assign_mssql_to_package call is checked against it from then on.
Questions about assign_mssql_to_package
Assign MSSQL database to hosting package. It is categorised as a Write tool in the 20i MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for assign_mssql_to_package: 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 20i MCP Server. Nothing to install.
assign_mssql_to_package 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 assign_mssql_to_package 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 assign_mssql_to_package. 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.
assign_mssql_to_package is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 20i MCP Server, and thousands of servers like it.
This server
Across the catalogue