Get Via ecosystem health: tools, memory, tasks, log.
AI agents call via_status to retrieve information from Via without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns status/health information about the Via ecosystem without modifying, executing, or deleting anything. It is purely informational retrieval. The blast radius of misuse is minimal—an attacker could only gain visibility into the current state of tools, memory, tasks, and logs, but could not alter or act upon that information through this tool alone.
From the tool's definition Tool name and description indicate retrieval of status information: 'Get Via ecosystem health: tools, memory, tasks, log.' The verb 'Get' and the context of querying ecosystem state (health checks, status monitoring) are characteristic of read-only operations…
Documented attack patterns abuse exactly the kind of access via_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Via, and nothing reaches the server without passing your rules. This is the rule we recommend for via_status:
{
"version": "1",
"default": "deny",
"tools": {
"via_status": {}
}
}via_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Via ecosystem health: tools, memory, tasks, log. It is categorised as a Read tool in the Via MCP Server, which means it retrieves data without modifying state.
Register the Via MCP server in PolicyLayer and add a rule for via_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 Via. Nothing to install.
via_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 via_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 via_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.
via_status is provided by the Via MCP server (vektor-memory/via). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Via, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Via tools catalogued and risk-classified — across an index of 43,000+ MCP servers.