convention

A read tool on the Claude Engram MCP server.

SERVERClaude Engram SOURCE20alexl/claude-engram

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/20alexl-claude-engram/convention.md

WHAT IT DOES

What convention does on Claude Engram

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

RISK

Why convention is rated Low

Without a description, confidence is reduced. The tool name suggests retrieval of convention data rather than modification, execution, or destruction. The server's purpose (persistent memory, session intelligence, pattern mining) indicates read-centric operations. Classified as Read with low severity because even if it accesses session history, it appears to be a query/retrieval function with no side effects.

From the tool's definition Tool name 'convention' with empty description provides no direct evidence of its function. Based on sibling tools in the server (audit_batch, context, memory, file_summarize, find_similar_issues, impact_analyze, pre_edit_check, scope, deps_map,…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs convention safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Engram, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For convention, this is the rule to start with:

convention Allowed

convention is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "convention": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Engram, apply this rule, and every convention call is checked against it from then on.

FAQ

Questions about convention

What does the convention tool do? +

convention is a read tool on the Claude Engram MCP server. It is categorised as a Read tool in the Claude Engram MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on convention? +

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

What risk level is convention? +

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

Can I rate-limit convention? +

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

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

convention is provided by the Claude Engram MCP server (20alexl/claude-engram). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Engram, and thousands of servers like it.

This server

All 16 Claude Engram tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →