Low Risk

bob_recent

Most recent turns within the last hours. Filter by src and/or role.

How to control bob_recent ↓

What bob_recent does on Brain

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

Low Risk

Why bob_recent needs a policy

This tool retrieves or queries data from indexed conversation history with optional filters (time window, source, role). It has no side effects—it does not create, modify, delete, or execute operations. It is a straightforward read operation over a searchable index of past conversations.

From the tool's definition Tool name and description indicate a retrieval operation: 'Most recent turns within the last `hours`. Filter by src and/or role.' The verb 'turns' and filtering options suggest querying conversation history without modification.

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

How to control bob_recent

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

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

bob_recent 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 Brain — 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 bob_recent

What does the bob_recent tool do? +

Most recent turns within the last hours. Filter by src and/or role. It is categorised as a Read tool in the Brain MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bob_recent? +

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

What risk level is bob_recent? +

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

Can I rate-limit bob_recent? +

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

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

bob_recent is provided by the Brain MCP server (mordechaipotash/brain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Brain tool call.

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

34 Brain 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.