list_oauth_credentials

SERVERDeloc SOURCEdelocdev/deloc-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deloc-mcp/list-oauth-credentials.md

WHAT IT DOES

What list_oauth_credentials does on Deloc

AI agents call list_oauth_credentials to retrieve information from Deloc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_oauth_credentials is rated Low

This tool retrieves metadata about OAuth credentials without modifying, executing, or deleting anything. Even though it involves credentials, the read-only nature and explicit redaction of secrets place it firmly in the Read category. Severity is low because the tool only lists credential metadata visible to the user and does not return sensitive secret values.

From the tool's definition Tool name 'list_oauth_credentials' and description states it 'List[s] OAuth credentials the authenticated user can see' — a query/retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_oauth_credentials safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_oauth_credentials, this is the rule to start with:

list_oauth_credentials Allowed

list_oauth_credentials is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_oauth_credentials": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Deloc, apply this rule, and every list_oauth_credentials call is checked against it from then on.

FAQ

Questions about list_oauth_credentials

What does the list_oauth_credentials tool do? +

List OAuth credentials the authenticated user can see. Org users see the team-shared credentials for their org; solo users see their personal credentials. Secret values (client_secret, password, private key) are NEVER returned. It is categorised as a Read tool in the Deloc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_oauth_credentials? +

Register the Deloc MCP server in PolicyLayer and add a rule for list_oauth_credentials: 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 list_oauth_credentials? +

list_oauth_credentials is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_oauth_credentials? +

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

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

list_oauth_credentials 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.

KEEP EXPLORING

More on Deloc, and thousands of servers like it.

This server

All 45 Deloc tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →