AI agents call ara_fon to retrieve information from Fonlar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name translates from Turkish as 'search fund', consistent with a read/query operation. The server is described as providing access to fund data queries with no write or execute capabilities mentioned. Confidence is lowered due to empty description.
From the tool's definition Tool name 'ara_fon' suggests a search/lookup operation (Turkish: 'ara' = search, 'fon' = fund). Server context is read-only investment fund data queries.
Documented attack patterns abuse exactly the kind of access ara_fon gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fonlar, and nothing reaches the server without passing your rules. This is the rule we recommend for ara_fon:
{
"version": "1",
"default": "deny",
"tools": {
"ara_fon": {}
}
}ara_fon 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.
ara_fon. It is categorised as a Read tool in the Fonlar MCP Server, which means it retrieves data without modifying state.
Register the Fonlar MCP server in PolicyLayer and add a rule for ara_fon: 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 Fonlar. Nothing to install.
ara_fon 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 ara_fon 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 ara_fon. 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.
ara_fon is provided by the Fonlar MCP server (maku-cpu/fonlar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fonlar, 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.
6 Fonlar tools catalogued and risk-classified — across an index of 43,000+ MCP servers.