contract-testing_admin_get_system_account_tokens
Retrieve API tokens for a system account (admin). Parameters: - accountId (string) *required*: UUID of the system account
This record as markdown: /tools/smartbear-mcp/contract-testing-admin-get-system-account-tokens.md
What contract-testing_admin_get_system_account_tokens does on SmartBear MCP
AI agents call contract-testing_admin_get_system_account_tokens to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
accountId | string | Yes | UUID of the system account |
Parameters from the server's own tool schema.
Why contract-testing_admin_get_system_account_tokens is rated Low
This is a Read operation—it retrieves data (API tokens) without side effects. However, severity is elevated to 'high' because the retrieved data are sensitive credentials (API tokens) that could enable unauthorized access to systems if leaked. An AI agent misusing this tool could expose authentication material, creating significant security risk despite the read-only nature of the operation.
From the tool's definition Tool name includes 'get' and description states 'Retrieve API tokens for a system account'. The action is retrieval with no modification or deletion.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs contract-testing_admin_get_system_account_tokens 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_get_system_account_tokens, this is the rule to start with:
contract-testing_admin_get_system_account_tokens is read-only, so it stays allowed. 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_get_system_account_tokens call is checked against it from then on.
Questions about contract-testing_admin_get_system_account_tokens
Retrieve API tokens for a system account (admin). Parameters: - accountId (string) *required*: UUID of the system account. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_admin_get_system_account_tokens accepts 1 parameter: accountId. Required: accountId. 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_get_system_account_tokens: 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_get_system_account_tokens is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the contract-testing_admin_get_system_account_tokens 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_get_system_account_tokens. 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_get_system_account_tokens 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