contract-testing_admin_create_system_account
Create a new system account (admin). Parameters: - name (string) *required*: Name of the system account
This record as markdown: /tools/smartbear-mcp/contract-testing-admin-create-system-account.md
What contract-testing_admin_create_system_account does on SmartBear MCP
AI agents use contract-testing_admin_create_system_account to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Name of the system account |
Parameters from the server's own tool schema.
Why contract-testing_admin_create_system_account is rated Medium
Creating a system account—especially an admin account—is a persistent, security-critical write operation that grants privileges and cannot be easily undone without administrative intervention. While not financial or destructive in the data-deletion sense, the blast radius is high because compromised admin credentials could lead to downstream system compromise.
From the tool's definition Tool name contains 'create' and description states 'Create a new system account (admin)'. This irreversibly adds a new administrative system account to the platform.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs contract-testing_admin_create_system_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_admin_create_system_account, this is the rule to start with:
contract-testing_admin_create_system_account 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 SmartBear MCP, apply this rule, and every contract-testing_admin_create_system_account call is checked against it from then on.
Questions about contract-testing_admin_create_system_account
Create a new system account (admin). Parameters: - name (string) *required*: Name of the system account. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
contract-testing_admin_create_system_account accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_admin_create_system_account: 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 SmartBear MCP. Nothing to install.
contract-testing_admin_create_system_account 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 contract-testing_admin_create_system_account 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 contract-testing_admin_create_system_account. 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.
contract-testing_admin_create_system_account is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue