AI agents use reexpress_add_true to create or update resources in Reexpress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Reexpress MCP Server environment.
The tool name pattern (add_*) combined with sibling tools like 'reexpress_file_set' and 'reexpress_file_clear' suggests this performs a write operation that modifies state reversibly. Without a description, confidence is reduced, but the naming convention and context of sibling write/management tools indicate this creates or updates data rather than reading or destructively removing it.
From the tool's definition Tool name 'reexpress_add_true' suggests adding or setting a value to true, implying data modification. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access reexpress_add_true gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Reexpress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for reexpress_add_true:
{
"version": "1",
"default": "deny",
"tools": {
"reexpress_add_true": {
"limits": [
{
"counter": "reexpress_add_true_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reexpress_add_true 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.
reexpress_add_true. It is categorised as a Write tool in the Reexpress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Reexpress MCP Server MCP server in PolicyLayer and add a rule for reexpress_add_true: 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 Reexpress MCP Server. Nothing to install.
reexpress_add_true 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 reexpress_add_true 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 reexpress_add_true. 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.
reexpress_add_true is provided by the Reexpress MCP Server MCP server (reexpressai/reexpress_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Reexpress MCP Server, 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.
9 Reexpress MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.