This record as markdown: /tools/io-github-kivanccakmak-yaver/op-get.md
What op_get does on Yaver
AI agents call op_get to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
item | string | Yes | Item name or ID |
vault | string | — |
Parameters from the server's own tool schema.
Why op_get is rated Low
The tool retrieves sensitive data (passwords, API keys, credentials stored in 1Password) from a credential vault. While the description notes passwords are masked, the tool still accesses and returns sensitive account information.
From the tool's definition Tool description states 'Look up a 1Password item (passwords masked)' — this is a retrieval operation that queries stored secrets/credentials.
Attacks that exploit this kind of access
The rule that runs op_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For op_get, this is the rule to start with:
op_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every op_get call is checked against it from then on.
Questions about op_get
Look up a 1Password item (passwords masked). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
op_get accepts 2 parameters: item, vault. Required: item. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for op_get: 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 Yaver. Nothing to install.
op_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the op_get 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 op_get. 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.
op_get is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue