FREE triage tool — send whatever context you have (message content, sender info, URLs, attachments, draft replies, thread messages, image/video URLs) and get back a prioritized list of which security tools to run. No AI call, no charge, instant response. Always call this first to get the best sec...
Risk signalsAccepts raw HTML/template content (body) · Accepts file system path (media[].filename) · Accepts URL/endpoint input (media[].url) · High parameter count (36 properties)
Part of the Agent Safe server.
Free to start. No card required.
AI agents invoke assess_message to trigger processes or run actions in Agent Safe. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
assess_message can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"assess_message": {
"limits": [
{
"counter": "assess_message_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Agent Safe policy for all 11 tools.
These attack patterns abuse exactly the kind of access assess_message gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
FREE triage tool — send whatever context you have (message content, sender info, URLs, attachments, draft replies, thread messages, image/video URLs) and get back a prioritized list of which security tools to run. No AI call, no charge, instant response. Always call this first to get the best security coverage.. It is categorised as a Execute tool in the Agent Safe MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agent Safe MCP server in PolicyLayer and add a rule for assess_message: 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 Agent Safe. Nothing to install.
assess_message is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the assess_message 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 assess_message. 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.
assess_message is provided by the Agent Safe MCP server (https://agentsafe.locationledger.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 Agent Safe tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.