Pull memory context formatted for an AI tool.
AI agents call via_context 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 retrieves or queries existing memory context data for use by AI tools. The verb 'pull' and the read-only nature of fetching pre-formatted context without altering system state places it squarely in the Read category. The severity is low because context retrieval poses minimal risk of harm—it accesses existing data without execution, deletion, or financial impact.
From the tool's definition Tool name 'via_context' and description 'Pull memory context formatted for an AI tool' indicate retrieval of stored context/memory data without modification or side effects.
Documented attack patterns abuse exactly the kind of access via_context 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_context:
{
"version": "1",
"default": "deny",
"tools": {
"via_context": {}
}
}via_context 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.
Pull memory context formatted for an AI tool. 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_context: 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_context 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_context 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_context. 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_context 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.