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

test_oauth_credential

Exchange credentials for a fresh access token against the upstream. Bypasses the server-side cache so you always see the live behavior — useful for verifying a newly created or rotated credential. Returns a short preview of the token (first 6 chars) plus the new cache expiry. The full token is ne...

SERVERDeloc SOURCEdelocdev/deloc-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deloc-mcp/test-oauth-credential.md

What test_oauth_credential does on Deloc

AI agents invoke test_oauth_credential to trigger actions in Deloc. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why test_oauth_credential is rated High

This tool actively triggers an external OAuth token exchange operation against an upstream identity provider, bypassing caching to force a live network call. It executes an external operation (credential exchange) whose effects depend on the provided arguments. It does not merely read stored data, nor does it create/modify persistent data — it executes a live authentication flow.

From the tool's definition Exchange credentials for a fresh access token against the upstream. Bypasses the server-side cache so you always see the live behavior

Questions about test_oauth_credential

What does the test_oauth_credential tool do? +

Exchange credentials for a fresh access token against the upstream. Bypasses the server-side cache so you always see the live behavior — useful for verifying a newly created or rotated credential. Returns a short preview of the token (first 6 chars) plus the new cache expiry. The full token is never exposed. It is categorised as a Execute tool in the Deloc MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_oauth_credential? +

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

What risk level is test_oauth_credential? +

test_oauth_credential is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_oauth_credential? +

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

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

test_oauth_credential is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Deloc, and thousands of servers like it.

// 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 Deloc'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.