New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

preview_sandman_gemma_candidates

Collect candidate memories for Gemma-based Sandman review. Does not call a model and does not write.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/preview-sandman-gemma-candidates.md

What preview_sandman_gemma_candidates does on Mapi Agent Memory

AI agents call preview_sandman_gemma_candidates to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why preview_sandman_gemma_candidates is rated Low

The tool explicitly states it only collects/retrieves candidate memories without writing or calling any model. This is a pure read/query operation with minimal blast radius.

From the tool's definition 'Collect candidate memories for Gemma-based Sandman review. Does not call a model and does not write.'

Questions about preview_sandman_gemma_candidates

What does the preview_sandman_gemma_candidates tool do? +

Collect candidate memories for Gemma-based Sandman review. Does not call a model and does not write. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on preview_sandman_gemma_candidates? +

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

What risk level is preview_sandman_gemma_candidates? +

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

Can I rate-limit preview_sandman_gemma_candidates? +

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

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

preview_sandman_gemma_candidates is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mapi Agent Memory, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mapi Agent Memory's. Pull the full record:

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.