🔄 Reauthenticate an existing remote MCP server connection. When an existing remote MCP server's OAuth tokens have expired or become invalid, use this tool to initiate a fresh authentication flow. This will start a new OAuth flow while preserving the server configuration. **Use this...
Part of the DataGen MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke ReAuthRemoteMcpServer to trigger processes or run actions in DataGen. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
ReAuthRemoteMcpServer can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
ReAuthRemoteMcpServer:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full DataGen policy for all 20 tools.
Agents calling execute-class tools like ReAuthRemoteMcpServer have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
ReAuthRemoteMcpServer is one of the high-risk operations in DataGen. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
🔄 Reauthenticate an existing remote MCP server connection. When an existing remote MCP server's OAuth tokens have expired or become invalid, use this tool to initiate a fresh authentication flow. This will start a new OAuth flow while preserving the server configuration. **Use this when:** - Server tools stop working due to expired tokens - You receive authentication errors from MCP tools - OAuth tokens need to be refreshed for a connected server - Server connection has been lost and needs re-authentication **Process:** 1. Call this tool with the server name (must follow naming rules) 2. If OAuth is required, you'll get an auth_url 3. Complete authentication in the browser 4. Use checkRemoteMcpOauthStatus to verify completion **Naming Rules:** - Use only alphanumeric characters (no spaces, underscores, or dashes) - Start with an uppercase letter - Use CamelCase for multiple words - Examples: 'GitHub', 'Slack', 'GoogleDrive', 'OpenAI' **Returns:** Either immediate success or OAuth flow details for browser authentication. It is categorised as a Execute tool in the DataGen MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for ReAuthRemoteMcpServer. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the DataGen MCP server.
ReAuthRemoteMcpServer is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ReAuthRemoteMcpServer rule in your Intercept 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 Intercept policy for ReAuthRemoteMcpServer. 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.
ReAuthRemoteMcpServer is provided by the DataGen MCP server (kuoyusheng/datagendev). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept