AI agents call extract_decisions 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 retrieves and extracts decision information from existing logs and session data. It performs no creation, modification, deletion, or execution of external operations. The blast radius of misuse is limited to potential information disclosure of decision history, which poses minimal risk. This is a standard read/query operation typical of memory retrieval systems.
From the tool's definition Tool name 'extract_decisions' and description 'Extract decisions from session/decision logs' indicate data retrieval without modification. The verb 'extract' combined with reading from logs/sessions is a query operation.
Documented attack patterns abuse exactly the kind of access extract_decisions 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 extract_decisions:
{
"version": "1",
"default": "deny",
"tools": {
"extract_decisions": {}
}
}extract_decisions 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.
Extract decisions from session/decision logs. 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 extract_decisions: 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.
extract_decisions 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 extract_decisions 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 extract_decisions. 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.
extract_decisions 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.