score_salience
Calculate 5-component relevance score for an entity: baseImportance, recencyBoost, frequencyBoost, contextRelevance, noveltyBoost. Use with format_with_salience_budget to score then format.
This record as markdown: /tools/danielsimonjr-memory-mcp/score-salience.md
What score_salience does on Enhanced Knowledge Graph Memory Server
AI agents call score_salience to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why score_salience is rated Low
score_salience retrieves and processes metadata from the knowledge graph to compute a numeric ranking. It has no side effects, creates no new records irreversibly, executes no external code, and moves no money. It is a read-like analytical function with negligible blast radius if misused by an agent.
From the tool's definition Tool calculates a 'relevance score' by analyzing stored entity properties (baseImportance, recencyBoost, frequencyBoost, contextRelevance, noveltyBoost).
Attacks that exploit this kind of access
The rule that runs score_salience safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For score_salience, this is the rule to start with:
score_salience is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every score_salience call is checked against it from then on.
Questions about score_salience
Calculate 5-component relevance score for an entity: baseImportance, recencyBoost, frequencyBoost, contextRelevance, noveltyBoost. Use with format_with_salience_budget to score then format. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for score_salience: 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 Enhanced Knowledge Graph Memory Server. Nothing to install.
score_salience is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the score_salience 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.
Set action: deny in the PolicyLayer policy for score_salience. 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.
score_salience is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue