binotel_list_calls_since

A read tool on the All MCP server.

SERVERAllmcp SOURCEPerception-Dynamics-Inc/allmcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/allmcp/binotel-list-calls-since.md

WHAT IT DOES

What binotel_list_calls_since does on Allmcp

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

RISK

Why binotel_list_calls_since is rated Low

The tool retrieves call records based on a timestamp filter. 'List' operations typically query and return data without modification. While the description is empty (lowering confidence slightly), the semantic meaning of 'list_calls_since' clearly indicates a retrieval operation that has no side effects. This aligns with the Read category for data queries.

From the tool's definition Tool name 'binotel_list_calls_since' indicates a list/retrieval operation with a time-based filter ('since').

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs binotel_list_calls_since safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Allmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For binotel_list_calls_since, this is the rule to start with:

binotel_list_calls_since Allowed

binotel_list_calls_since is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "binotel_list_calls_since": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Allmcp, apply this rule, and every binotel_list_calls_since call is checked against it from then on.

FAQ

Questions about binotel_list_calls_since

What does the binotel_list_calls_since tool do? +

binotel_list_calls_since is a read tool on the All MCP server. It is categorised as a Read tool in the Allmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on binotel_list_calls_since? +

Register the All MCP server in PolicyLayer and add a rule for binotel_list_calls_since: 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 Allmcp. Nothing to install.

What risk level is binotel_list_calls_since? +

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

Can I rate-limit binotel_list_calls_since? +

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

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

binotel_list_calls_since is provided by the All MCP server (Perception-Dynamics-Inc/allmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on All, and thousands of servers like it.

This server

All 501 All tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →