Evervault MCP integration for AI agents.
Connect AI agents to Evervault through 3 structured actions, including inspect token, decrypt json, and encrypt json. Review authentication, inputs, workflow…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Evervault integration exposes
The Evervault Agent App exposes 3 provider-backed actions for developer tools and security work. Its current contract lets an authorized agent inspect metadata for an evervault-encrypted token without decrypting it, decrypt an evervault-encrypted json-compatible value, and encrypt a json-compatible value with the configured evervault app. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Evervault account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Evervault capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
inspect_tokenREADInspect metadata for an Evervault-encrypted token without decrypting it.
INPUTS: token
decrypt_jsonREVIEWDecrypt an Evervault-encrypted JSON-compatible value.
INPUTS: value
encrypt_jsonREVIEWEncrypt a JSON-compatible value with the configured Evervault app.
INPUTS: value
INPUT CONTRACTS
Know what the action needs before it runs.
inspect_token
tokenOPTIONAL- The Evervault-encrypted token to inspect.
decrypt_json
valueOPTIONAL- A JSON-compatible value, including objects, arrays, scalars, or null.
encrypt_json
valueOPTIONAL- A JSON-compatible value, including objects, arrays, scalars, or null.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Inspect Token
Inspect metadata for an Evervault-encrypted token without decrypting it. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
inspect_tokenVerify with Decrypt Json
Decrypt an Evervault-encrypted JSON-compatible value. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
decrypt_jsonSAFETY BOUNDARY
Operate Evervault with explicit limits
- Authorize Evervault with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Evervault data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Evervault rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Evervault task completed successfully.
CONNECTION MODEL
API key
Evervault API key from App Settings > API Keys: https://app.evervault.com
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Evervault.