vs_memory_get

Retrieve workspace-scoped memory entries for Mutly workflows.

Server VibeServe ncsound919/vibeserve
Category Read
Risk class Low
Parameters 00 required

What vs_memory_get does on VibeServe

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

Why vs_memory_get needs a policy

This tool retrieves memory entries without any ability to modify, delete, or execute operations. It is a simple data retrieval function scoped to workspace memory, consistent with the 'Read' category for tools that query or retrieve data with no side effects.

From the tool's definition The tool description explicitly states 'Retrieve workspace-scoped memory entries', which is a read operation with no modification of data.

Questions about vs_memory_get

What does the vs_memory_get tool do? +

Retrieve workspace-scoped memory entries for Mutly workflows. It is categorised as a Read tool in the VibeServe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on vs_memory_get? +

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

What risk level is vs_memory_get? +

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

Can I rate-limit vs_memory_get? +

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

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

vs_memory_get is provided by the VibeServe MCP server (ncsound919/vibeserve). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.