AI agents use mesh_send to create or update resources in Qualixar/superlocalmemory — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Qualixar/superlocalmemory environment.
The name 'mesh_send' indicates an operation that dispatches data, consistent with Write category (creates or modifies data). However, the empty description creates uncertainty about exact side effects and scope. The tool operates within a memory management system with multi-channel retrieval, suggesting it may distribute memory entries across a mesh infrastructure.
From the tool's definition Tool name 'mesh_send' suggests transmission or distribution of data across a network mesh. Within a persistent memory server context, this likely creates or modifies data by sending memory records to other nodes or destinations.
Documented attack patterns abuse exactly the kind of access mesh_send gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Qualixar/superlocalmemory, and nothing reaches the server without passing your rules. This is the rule we recommend for mesh_send:
{
"version": "1",
"default": "deny",
"tools": {
"mesh_send": {
"limits": [
{
"counter": "mesh_send_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}mesh_send 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.
mesh_send. It is categorised as a Write tool in the Qualixar/superlocalmemory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Qualixar/superlocalmemory MCP server in PolicyLayer and add a rule for mesh_send: 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 Qualixar/superlocalmemory. Nothing to install.
mesh_send 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 mesh_send 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 mesh_send. 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.
mesh_send is provided by the Qualixar/superlocalmemory MCP server (qualixar/superlocalmemory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 59 Qualixar/superlocalmemory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
59 Qualixar/superlocalmemory tools catalogued and risk-classified — across an index of 42,500+ MCP servers.