use_credential · Psamvault MCP: Risk & Policy

WHAT IT DOES

What use_credential does on Psamvault

AI agents invoke use_credential to trigger actions in Psamvault. 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 IT NEEDS A POLICY

Why use_credential needs a policy

The tool executes outbound HTTP requests authenticated with stored credentials. This is an Execute category because it triggers external network operations whose effects depend on the arguments (target URL, method, payload).

From the tool's definition 'Make an authenticated HTTP request using a credential stored in psamvault' — this triggers an external HTTP operation using stored credentials

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

use_credential Rate-limited

use_credential stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "use_credential": {
      "limits": [
        {
          "counter": "use_credential_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Psamvault, so you can run agents against it safely.

FAQ

Questions about use_credential

What does the use_credential tool do? +

[🔑 API Key Operations] Make an authenticated HTTP request using a credential stored in psamvault. It is categorised as a Execute tool in the Psamvault MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on use_credential? +

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

What risk level is use_credential? +

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

Can I rate-limit use_credential? +

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

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

use_credential is provided by the Psamvault MCP server (psam-717/psamvault-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.