realestate.walkscore.score
Walk Score (0-100), Transit Score (0-100), and Bike Score (0-100) for any US/Canada address. Measures walkability to amenities, public transit quality, and cycling infrastructure. Industry-standard walkability metric used by 30,000+ websites (Walk Score / Redfin)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/realestate.walkscore.score.md
What realestate.walkscore.score does on Apibase
AI agents call realestate.walkscore.score to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
address | string | Yes | Full street address, e.g. "1119 8th Avenue Seattle WA 98101" |
latitude | number | Yes | Latitude of the address (-90 to 90). Use geo.geocode to get coordinates. |
longitude | number | Yes | Longitude of the address (-180 to 180). Use geo.geocode to get coordinates. |
Parameters from the server's own tool schema.
Why realestate.walkscore.score is rated Low
Retrieves published walkability metrics for addresses; no side effects or data modification.
From the tool's definition Walk Score, Transit Score, Bike Score for any US/Canada address. Measures walkability.
Attacks that exploit this kind of access
The rule that runs realestate.walkscore.score safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For realestate.walkscore.score, this is the rule to start with:
realestate.walkscore.score is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every realestate.walkscore.score call is checked against it from then on.
Questions about realestate.walkscore.score
Walk Score (0-100), Transit Score (0-100), and Bike Score (0-100) for any US/Canada address. Measures walkability to amenities, public transit quality, and cycling infrastructure. Industry-standard walkability metric used by 30,000+ websites (Walk Score / Redfin). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
realestate.walkscore.score accepts 3 parameters: address, latitude, longitude. Required: address, latitude, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for realestate.walkscore.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 Apibase. Nothing to install.
realestate.walkscore.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 realestate.walkscore.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 realestate.walkscore.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.
realestate.walkscore.score is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue