AI agents call staleness_check to retrieve information from Sfgraph without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Staleness checks query metadata or sync status without modifying data or executing operations. Within the sfgraph context—a local, privacy-first knowledge graph that syncs Salesforce org data—this tool appears to assess freshness/currency of indexed information, a typical read operation. No evidence of side effects, code execution, deletion, or financial impact.
From the tool's definition Tool name 'staleness_check' and context of sibling tools (analyze_field, explain_code, find_nodes, find_similar, freshness_report) all indicate read-only queries. Description is truncated ('USE THIS for any') but insufficient to suggest mutations or execution.
Attacks that exploit this kind of access
USE THIS for any. It is categorised as a Read tool in the Sfgraph MCP Server, which means it retrieves data without modifying state.
Register the Sfgraph MCP server in PolicyLayer and add a rule for staleness_check: 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 Sfgraph. Nothing to install.
staleness_check 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 staleness_check 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 staleness_check. 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.
staleness_check is provided by the Sfgraph MCP server (ryanstark24/sfgraph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
staleness_check is one line of Sfgraph's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →