request_protected_credential
Ask the operator to enter a credential for one or more explicitly named destination hosts. Returns request metadata only; the secret is stored in the protected local vault and can be referenced by credentialId in web_fetch or http_request.
This record as markdown: /tools/cowork-os/request-protected-credential.md
What request_protected_credential does on CoWork OS
AI agents use request_protected_credential to create or update resources in CoWork OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CoWork OS environment.
Why request_protected_credential is rated Medium
Creates reversible credential storage entries in protected vault; enables subsequent authenticated access.
From the tool's definition Ask operator to enter credential, stored in protected vault, referenced by credentialId
Attacks that exploit this kind of access
The rule that runs request_protected_credential safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CoWork OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For request_protected_credential, this is the rule to start with:
request_protected_credential 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 CoWork OS, apply this rule, and every request_protected_credential call is checked against it from then on.
Questions about request_protected_credential
Ask the operator to enter a credential for one or more explicitly named destination hosts. Returns request metadata only; the secret is stored in the protected local vault and can be referenced by credentialId in web_fetch or http_request. It is categorised as a Write tool in the CoWork OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CoWork OS MCP server in PolicyLayer and add a rule for request_protected_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 CoWork OS. Nothing to install.
request_protected_credential 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 request_protected_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.
Set action: deny in the PolicyLayer policy for request_protected_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.
request_protected_credential is provided by the CoWork OS MCP server (CoWork-OS/CoWork-OS). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CoWork OS, and thousands of servers like it.
This server
Across the catalogue