New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

reset_oauth_client_secret

Reset an OAuth client secret

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about reset_oauth_client_secret

What does the reset_oauth_client_secret tool do? +

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.

How do I enforce a policy on reset_oauth_client_secret? +

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.

What risk level is reset_oauth_client_secret? +

reset_oauth_client_secret is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reset_oauth_client_secret? +

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.

How do I block reset_oauth_client_secret completely? +

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.

What MCP server provides reset_oauth_client_secret? +

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.

Across the catalogue

// 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 Linode MCP Server'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.