AI agents call Profile to retrieve information from Phalcon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is reduced. The name 'Profile' suggests a read operation (retrieving profile data), which is the least severe category. However, given the context of sibling tools related to blockchain operations (BalanceChange, StateChange, TransactionOverview, Trace), this could potentially relate to blockchain profile queries.
From the tool's definition Tool name is 'Profile' with empty description. Based on naming convention alone, 'Profile' typically retrieves or displays user/entity information without modification.
Documented attack patterns abuse exactly the kind of access Profile 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 Profile:
{
"version": "1",
"default": "deny",
"tools": {
"Profile": {}
}
}Profile is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Profile. It is categorised as a Read tool in the Phalcon MCP Server, which means it retrieves data without modifying state.
Register the Phalcon MCP server in PolicyLayer and add a rule for Profile: 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.
Profile 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 Profile 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 Profile. 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.
Profile 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.