call_status
Estado del servidor de llamadas: si hay grabación activa y quiénes están en la sala. Retorna { recording, room, startedAt, participants[] }. Útil para saber si la llamada sigue viva antes de grabar o destruir.
This record as markdown: /tools/cloud-easybits-easybits/call-status.md
What call_status does on EasyBits
AI agents call call_status to retrieve information from EasyBits without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why call_status is rated Low
Retrieves call server state and participant information without modifying or executing operations.
From the tool's definition Estado, si hay grabación, quiénes están, Retorna. Query call status without side effects.
Attacks that exploit this kind of access
The rule that runs call_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EasyBits, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For call_status, this is the rule to start with:
call_status 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 EasyBits, apply this rule, and every call_status call is checked against it from then on.
Questions about call_status
Estado del servidor de llamadas: si hay grabación activa y quiénes están en la sala. Retorna { recording, room, startedAt, participants[] }. Útil para saber si la llamada sigue viva antes de grabar o destruir. It is categorised as a Read tool in the EasyBits MCP Server, which means it retrieves data without modifying state.
Register the EasyBits MCP server in PolicyLayer and add a rule for call_status: 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 EasyBits. Nothing to install.
call_status 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 call_status 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 call_status. 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.
call_status is provided by the EasyBits MCP server (@easybits.cloud/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EasyBits, and thousands of servers like it.
This server
Across the catalogue