reset_oauth_client_secret
Reset an OAuth client secret
This record as markdown: /tools/takashito-linode-mcp-server/reset-oauth-client-secret.md
What reset_oauth_client_secret does on Linode MCP Server
AI agents use reset_oauth_client_secret to create or update resources in Linode MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.
Why reset_oauth_client_secret is rated Medium
Resetting an OAuth client secret modifies a security credential, invalidating the old secret and generating a new one. This is a Write operation (creates new secret value) rather than Destructive since the client itself isn't deleted. However, severity is high because misuse could break all applications using the old secret or allow an attacker to take over OAuth flows.
From the tool's definition Reset an OAuth client secret
Attacks that exploit this kind of access
The rule that runs reset_oauth_client_secret safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reset_oauth_client_secret, this is the rule to start with:
reset_oauth_client_secret stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every reset_oauth_client_secret call is checked against it from then on.
Questions about reset_oauth_client_secret
Reset an OAuth client secret. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Linode MCP Server MCP server in PolicyLayer and add a rule for reset_oauth_client_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 Linode MCP Server. Nothing to install.
reset_oauth_client_secret is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the reset_oauth_client_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.
Set action: deny in the PolicyLayer policy for reset_oauth_client_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.
reset_oauth_client_secret is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue