gateway_capabilities

Personal Agent Gateway: list one connector's read capabilities — id, verb, expected params, and answerSchema — so you know what gateway_query can call on it. No secrets.

Server Yaver yaver-cli
Category Read
Risk class Low
Parameters 11 required

What gateway_capabilities does on Yaver

AI agents call gateway_capabilities to retrieve information from Yaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
connector string Yes Connector id

Parameters from the server's own tool schema.

Why gateway_capabilities needs a policy

Even though gateway_capabilities only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about gateway_capabilities

What does the gateway_capabilities tool do? +

Personal Agent Gateway: list one connector's read capabilities — id, verb, expected params, and answerSchema — so you know what gateway_query can call on it. No secrets. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does gateway_capabilities accept? +

gateway_capabilities accepts 1 parameter: connector. Required: connector. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gateway_capabilities? +

Register the Yaver MCP server in PolicyLayer and add a rule for gateway_capabilities: 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.

What risk level is gateway_capabilities? +

gateway_capabilities is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gateway_capabilities? +

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

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

gateway_capabilities 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.