83 tools. 0 can modify or destroy data without limits.
Read-only server. Low risk, but rate limits prevent runaway API costs.
Last updated:
Verified server · catalogue entry verified 27/06/2026 · full schemas captured for 79 of 83 tools
Running more than one server? Check your whole stack →
Full per-tool breakdown → Model it in the token calculator →
Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataforseo, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"backlinks_bulk_new_lost_backlinks": {
"limits": [
{
"counter": "backlinks_bulk_new_lost_backlinks_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
The Dataforseo server is primarily read-only with 83 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.
83 tools across 3 categories: Execute, Read, Write. 83 are read-only. 0 can modify, create, or delete data.
Register the Dataforseo MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 83 Dataforseo tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
83 Dataforseo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.