Returns the last successful poll time and staleness for each connected integration. Read-only; does not trigger any polls.
AI agents call get_freshness to retrieve information from Slopweaver without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves metadata about integration polling status. It queries state information without modifying, executing, or deleting anything. The 'read-only' declaration and absence of any action verbs (create, update, delete, execute) confirm this is a Read category tool with minimal risk.
From the tool's definition The description explicitly states 'Returns the last successful poll time and staleness for each connected integration' and 'Read-only; does not trigger any polls.' This is a pure query operation with no side effects.
Attacks that exploit this kind of access
Returns the last successful poll time and staleness for each connected integration. Read-only; does not trigger any polls. It is categorised as a Read tool in the Slopweaver MCP Server, which means it retrieves data without modifying state.
Register the Slopweaver MCP server in PolicyLayer and add a rule for get_freshness: 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 Slopweaver. Nothing to install.
get_freshness 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 get_freshness 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 get_freshness. 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.
get_freshness is provided by the Slopweaver MCP server (slopweaver/slopweaver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →