Low Risk

memory_tags

List all memory tags with counts.

How to control memory_tags ↓

What memory_tags does on Project Tessera

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

Low Risk

Why memory_tags needs a policy

This is a simple metadata retrieval tool that enumerates tags and their usage counts from the workspace memory system. It has no side effects, does not execute code or external operations, does not create or modify data, and does not delete anything. The blast radius of misuse is minimal—an AI agent listing tags cannot cause harm beyond potentially learning what memory categories exist in the workspace.

From the tool's definition Tool is described as 'List all memory tags with counts' — a query operation that retrieves metadata about existing tags without modifying, deleting, or executing anything. The verb 'list' is characteristic of Read operations.

Documented attack patterns abuse exactly the kind of access memory_tags gives an agent:

How to control memory_tags

PolicyLayer is an MCP gateway — it sits between your AI agents and Project Tessera, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_tags:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_tags": {}
  }
}

memory_tags is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Project Tessera — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about memory_tags

What does the memory_tags tool do? +

List all memory tags with counts. It is categorised as a Read tool in the Project Tessera MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on memory_tags? +

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

What risk level is memory_tags? +

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

Can I rate-limit memory_tags? +

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

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

memory_tags is provided by the Project Tessera MCP server (besslframework-stack/project-tessera). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Project Tessera tool call.

Start from Project Tessera, 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.

43 Project Tessera tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.