Retrieve a report of activity records from the Vonage Reports API. Supports date-based queries (e.g. "all SMS sent over the last week") and ID-based queries (e.g. "report for Call ID 1234-abcd"). For date-based queries provide product, direction (required for SMS/MESSAGES), and optionally date_st...
High parameter count (12 properties)
Part of the Vonage Mcp Server Api Bindings MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get-records-report to retrieve information from Vonage Mcp Server Api Bindings without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get-records-report only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
get-records-report:
rules:
- action: allowSee the full Vonage Mcp Server Api Bindings policy for all 13 tools.
Agents calling read-class tools like get-records-report have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Retrieve a report of activity records from the Vonage Reports API. Supports date-based queries (e.g. "all SMS sent over the last week") and ID-based queries (e.g. "report for Call ID 1234-abcd"). For date-based queries provide product, direction (required for SMS/MESSAGES), and optionally date_start/date_end. For ID-based queries provide product and id (comma-separated UUIDs, max 20).. It is categorised as a Read tool in the Vonage Mcp Server Api Bindings MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get-records-report. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Vonage Mcp Server Api Bindings MCP server.
get-records-report 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 get-records-report rule in your Intercept 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 Intercept policy for get-records-report. 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.
get-records-report is provided by the Vonage Mcp Server Api Bindings MCP server (@vonage/vonage-mcp-server-api-bindings). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept