Check for stale documents exceeding the age threshold.
AI agents call check_document_freshness to retrieve information from Project Tessera without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries document age properties against a threshold to determine freshness status. It is a read-only information retrieval operation with no side effects on the documents themselves—it does not delete, modify, or execute actions. The local workspace memory context and sibling tools (health_check, digest_conversation, deep_recall) confirm this server performs informational operations.
From the tool's definition Tool performs a check operation to identify stale documents by age threshold. The description uses 'Check for' and 'exceeding', indicating a retrieval/query function that examines document metadata without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access check_document_freshness gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Project Tessera, and nothing reaches the server without passing your rules. This is the rule we recommend for check_document_freshness:
{
"version": "1",
"default": "deny",
"tools": {
"check_document_freshness": {}
}
}check_document_freshness is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check for stale documents exceeding the age threshold. It is categorised as a Read tool in the Project Tessera MCP Server, which means it retrieves data without modifying state.
Register the Project Tessera MCP server in PolicyLayer and add a rule for check_document_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 Project Tessera. Nothing to install.
check_document_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 check_document_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 check_document_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.
check_document_freshness is provided by the Project Tessera MCP server (besslframework-stack/project-tessera). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Project Tessera, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
43 Project Tessera tools catalogued and risk-classified — across an index of 43,000+ MCP servers.