convex_local_status
Check if the local self-hosted Convex backend is running (port 3210).
This record as markdown: /tools/io-github-kivanccakmak-yaver/convex-local-status.md
What convex_local_status does on Yaver
AI agents call convex_local_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why convex_local_status is rated Low
This tool retrieves the operational status of a local service by checking its port availability. It performs a read-only query with no ability to modify, execute code, delete data, or affect financial operations. The blast radius of misuse is minimal—an agent cannot cause harm by repeatedly checking service status.
From the tool's definition Tool name 'convex_local_status' and description 'Check if the local self-hosted Convex backend is running' indicate a status query operation with no side effects.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs convex_local_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convex_local_status, this is the rule to start with:
convex_local_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 Yaver, apply this rule, and every convex_local_status call is checked against it from then on.
Questions about convex_local_status
Check if the local self-hosted Convex backend is running (port 3210). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
convex_local_status accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for convex_local_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 Yaver. Nothing to install.
convex_local_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 convex_local_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 convex_local_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.
convex_local_status 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.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue