Simulate how submitting a trace would affect an agent's trust score WITHOUT writing to the database. Returns projected new score, delta, and tier change. Use this for what-if analysis before submitting traces.
Part of the Garl Protocol server.
Free to start. No card required.
AI agents call garl_simulate_score to retrieve information from Garl Protocol without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though garl_simulate_score only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"garl_simulate_score": {}
}
}See the full Garl Protocol policy for all 28 tools.
These attack patterns abuse exactly the kind of access garl_simulate_score gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Simulate how submitting a trace would affect an agent's trust score WITHOUT writing to the database. Returns projected new score, delta, and tier change. Use this for what-if analysis before submitting traces.. It is categorised as a Read tool in the Garl Protocol MCP Server, which means it retrieves data without modifying state.
Register the Garl Protocol MCP server in PolicyLayer and add a rule for garl_simulate_score: 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 Garl Protocol. Nothing to install.
garl_simulate_score 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 garl_simulate_score 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 garl_simulate_score. 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.
garl_simulate_score is provided by the Garl Protocol MCP server (@garl-protocol/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 28 Garl Protocol 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.