AI agents call get_city_dashboard to retrieve information from Fdl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves aggregated dashboard data (counts, scores, rankings, breakdowns) for a geographic region. It performs no creation, modification, deletion, code execution, or financial operations. The 'Get' verb and read-only nature of returning statistics and performance metrics confirm this as a Read category tool with low severity.
From the tool's definition Tool name 'get_city_dashboard' and description 'Get the small business web-quality dashboard for a US city. Returns audited site count, mean score, top/bottom performers, and niche breakdown.' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get the small business web-quality dashboard for a US city. Returns audited site count, mean score, top/bottom performers, and niche breakdown. It is categorised as a Read tool in the Fdl MCP Server, which means it retrieves data without modifying state.
Register the Fdl MCP server in PolicyLayer and add a rule for get_city_dashboard: 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 Fdl. Nothing to install.
get_city_dashboard 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 get_city_dashboard 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 get_city_dashboard. 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.
get_city_dashboard is provided by the Fdl MCP server (nareshdevelop/fdl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_city_dashboard is one line of Fdl's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →