AI agents use import_from_ai to create or update resources in Project Tessera — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Tessera environment.
The tool imports external data into the local memory system, which constitutes creation or modification of stored data. This is reversible (imported data can be deleted or replaced), so it falls under Write rather than Destructive or Execute.
From the tool's definition Tool name 'import_from_ai' and description 'Import memories from another AI tool's export' indicate data ingestion and storage into the vector store/memory system. This is a create/write operation that adds or modifies data in the workspace memory.
Documented attack patterns abuse exactly the kind of access import_from_ai 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 import_from_ai:
{
"version": "1",
"default": "deny",
"tools": {
"import_from_ai": {
"limits": [
{
"counter": "import_from_ai_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_from_ai stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Import memories from another AI tool's export. It is categorised as a Write tool in the Project Tessera MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project Tessera MCP server in PolicyLayer and add a rule for import_from_ai: 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.
import_from_ai is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the import_from_ai 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 import_from_ai. 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.
import_from_ai 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.