clear_instance_voice_settings
Drop a subscribed instance
This record as markdown: /tools/io-github-proagentstore-platform/clear-instance-voice-settings.md
What clear_instance_voice_settings does on ProAgentStore
AI agents call clear_instance_voice_settings to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_instance_voice_settings is rated Critical
Permanently deletes instance voice settings, preventing recovery without manual reconfiguration.
From the tool's definition Drop a subscribed instance; irreversibly removes subscription configuration.
Attacks that exploit this kind of access
The rule that runs clear_instance_voice_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clear_instance_voice_settings, this is the rule to start with:
clear_instance_voice_settings is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every clear_instance_voice_settings call is checked against it from then on.
Questions about clear_instance_voice_settings
Drop a subscribed instance. It is categorised as a Destructive tool in the ProAgentStore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for clear_instance_voice_settings: 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 ProAgentStore. Nothing to install.
clear_instance_voice_settings is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_instance_voice_settings 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 clear_instance_voice_settings. 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.
clear_instance_voice_settings is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue