contract-testing_delete_secret

Delete a secret by UUID. Parameters: - secretId (string) *required*: UUID of the secret

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/contract-testing-delete-secret.md

What contract-testing_delete_secret does on SmartBear MCP

AI agents call contract-testing_delete_secret to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
secretId string Yes UUID of the secret

Parameters from the server's own tool schema.

Why contract-testing_delete_secret is rated Critical

This tool permanently deletes data (a secret) with no recovery mechanism. Deletion operations that cannot be undone fall squarely into the Destructive category. The severity is high because an AI agent with access to this tool could delete critical secrets used for authentication, API keys, or other sensitive credentials, causing service disruption or security compromise.

From the tool's definition Tool name contains 'delete' and description states 'Delete a secret by UUID.' The action irreversibly removes a secret resource.

Questions about contract-testing_delete_secret

What does the contract-testing_delete_secret tool do? +

Delete a secret by UUID. Parameters: - secretId (string) *required*: UUID of the secret. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does contract-testing_delete_secret accept? +

contract-testing_delete_secret accepts 1 parameter: secretId. Required: secretId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on contract-testing_delete_secret? +

Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_delete_secret: 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.

What risk level is contract-testing_delete_secret? +

contract-testing_delete_secret is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit contract-testing_delete_secret? +

Yes. Add a rate_limit block to the contract-testing_delete_secret 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.

How do I block contract-testing_delete_secret completely? +

Set action: deny in the PolicyLayer policy for contract-testing_delete_secret. 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.

What MCP server provides contract-testing_delete_secret? +

contract-testing_delete_secret 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of SmartBear's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.