ops_verbs
List every registered ops verb with its description, payload schema, whether it streams, and whether guests may call it. Call this once to populate the agent's knowledge of the ops API.
This record as markdown: /tools/io-github-kivanccakmak-yaver/ops-verbs.md
What ops_verbs does on Yaver
AI agents call ops_verbs 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.
Why ops_verbs is rated Low
This is a purely informational tool that retrieves a catalog of available operations and their metadata. It has no side effects, creates no resources, modifies no state, and executes no external code. It is a classic Read operation: querying an API to discover available endpoints and their schemas.
From the tool's definition Tool name 'ops_verbs' and description indicate it 'List[s] every registered ops verb' — a query operation that retrieves and enumerates metadata about available operations.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs ops_verbs 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 ops_verbs, this is the rule to start with:
ops_verbs 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 ops_verbs call is checked against it from then on.
Questions about ops_verbs
List every registered ops verb with its description, payload schema, whether it streams, and whether guests may call it. Call this once to populate the agent's knowledge of the ops API. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
Register the Yaver MCP server in PolicyLayer and add a rule for ops_verbs: 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.
ops_verbs 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 ops_verbs 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 ops_verbs. 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.
ops_verbs 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