Critical Risk →

reset_connector_token

Reset connector auth state for the current user. Use when tokens are stale, missing scopes, tied to the wrong account/workspace, or repeatedly failing auth. For credential-based connectors, this clears the saved credentials so the user can re-enter them. Input: connector_id (required). Supported ...

Part of the CorpusIQ server.

reset_connector_token can permanently delete data in CorpusIQ, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE CORPUSIQ →

Free to start. No card required.

AI agents may call reset_connector_token to permanently remove or destroy resources in CorpusIQ. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call reset_connector_token in a loop, permanently destroying resources in CorpusIQ. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "reset_connector_token"
  ]
}

See the full CorpusIQ policy for all 60 tools.

Get this rule live on your own CorpusIQ server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY CORPUSIQ →

View all 60 tools →

These attack patterns abuse exactly the kind of access reset_connector_token gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so reset_connector_token only ever does what you allow.

SECURE CORPUSIQ →

Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the reset_connector_token tool do? +

Reset connector auth state for the current user. Use when tokens are stale, missing scopes, tied to the wrong account/workspace, or repeatedly failing auth. For credential-based connectors, this clears the saved credentials so the user can re-enter them. Input: connector_id (required). Supported values: google_workspace, microsoft, dropbox, shopify, quickbooks, hubspot, slack, ebay, facebook_marketing, tiktok, klaviyo, calendly, activecampaign, odoo, constantcontact, airtable, gohighlevel, monday, semrush, ahrefs, posthog, stripe, gunbroker.. It is categorised as a Destructive tool in the CorpusIQ MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on reset_connector_token? +

Register the CorpusIQ MCP server in PolicyLayer and add a rule for reset_connector_token: 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 CorpusIQ. Nothing to install.

What risk level is reset_connector_token? +

reset_connector_token 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 reset_connector_token? +

Yes. Add a rate_limit block to the reset_connector_token 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 reset_connector_token completely? +

Set action: deny in the PolicyLayer policy for reset_connector_token. 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 reset_connector_token? +

reset_connector_token is provided by the CorpusIQ MCP server (https://mcp2.corpusiq.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CorpusIQ tool call.

Deterministic rules across all 60 CorpusIQ tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.