AI agents call Trace as a supporting operation in Phalcon workflows.
With no description available, classification is uncertain. Based on sibling tools in a blockchain analytics context, 'Trace' most plausibly reads/queries transaction trace information, placing it in the Read category. However, due to the empty description, confidence is low and I'm defaulting to Other to reflect the ambiguity.
From the tool's definition Tool name is 'Trace' with an empty description. Sibling tools suggest blockchain/transaction analysis context (TransactionOverview, BalanceChange, StateChange), so 'Trace' likely retrieves transaction trace data.
Documented attack patterns abuse exactly the kind of access Trace gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Phalcon, and nothing reaches the server without passing your rules. This is the rule we recommend for Trace:
{
"version": "1",
"default": "deny",
"tools": {
"Trace": {
"limits": [
{
"counter": "trace_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}Trace gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Trace. It is categorised as a Other tool in the Phalcon MCP Server, which means it performs auxiliary operations.
Register the Phalcon MCP server in PolicyLayer and add a rule for Trace: 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 Phalcon. Nothing to install.
Trace is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the Trace 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 Trace. 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.
Trace is provided by the Phalcon MCP server (mark3labs/phalcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Phalcon, 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.
7 Phalcon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.