Export extracted data to JSON format
AI agents use export_to_json to create or update resources in Pydoll — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pydoll environment.
This tool creates or modifies data in a reversible manner (JSON export). It does not permanently delete data (not Destructive), does not execute arbitrary code (not Execute), involves no financial operations (not Financial), and simply structures existing data for output (not Read, as it creates new formatted output).
From the tool's definition Tool description states 'Export extracted data to JSON format', which involves creating/writing a new JSON file or data structure from existing extracted data.
Documented attack patterns abuse exactly the kind of access export_to_json gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for export_to_json:
{
"version": "1",
"default": "deny",
"tools": {
"export_to_json": {
"limits": [
{
"counter": "export_to_json_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_to_json stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export extracted data to JSON format. It is categorised as a Write tool in the Pydoll MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pydoll MCP server in PolicyLayer and add a rule for export_to_json: 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 Pydoll. Nothing to install.
export_to_json is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the export_to_json 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 export_to_json. 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.
export_to_json is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, 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.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.