integrations_test

Send a test notification to verify an integration is working. Specify a channel or omit to test all.

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

What integrations_test does on Yaver

AI agents call integrations_test 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
channel string Channel to test (telegram, discord, slack, teams, linear, jira, pagerduty, opsgenie, email). Omit to test all.

Parameters from the server's own tool schema.

Why integrations_test needs a policy

Even though integrations_test 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 integrations_test

What does the integrations_test tool do? +

Send a test notification to verify an integration is working. Specify a channel or omit to test all. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does integrations_test accept? +

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

How do I enforce a policy on integrations_test? +

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

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

Can I rate-limit integrations_test? +

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

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

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