dr_export_to_sheet
Append graded sessions to a Google Sheet. Customer creates a sheet, shares it with the OAuth account, and pastes the spreadsheet_id here (or stores it on the account). Each row: [graded_at, session_id, click_id_value, click_id_type, network, page_url, grade, numeric_score, ad_network_signal_type,...
This record as markdown: /tools/io-github-0nork-0nmcp/dr-export-to-sheet.md
What dr_export_to_sheet does on 0nmcp
AI agents use dr_export_to_sheet to create or update resources in 0nmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 0nmcp environment.
Why dr_export_to_sheet is rated Medium
An AI agent can call dr_export_to_sheet faster than any human can review: one bad instruction and it creates or modifies resources in 0nmcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs dr_export_to_sheet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dr_export_to_sheet, this is the rule to start with:
dr_export_to_sheet 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 0nmcp, apply this rule, and every dr_export_to_sheet call is checked against it from then on.
Questions about dr_export_to_sheet
Append graded sessions to a Google Sheet. Customer creates a sheet, shares it with the OAuth account, and pastes the spreadsheet_id here (or stores it on the account). Each row: [graded_at, session_id, click_id_value, click_id_type, network, page_url, grade, numeric_score, ad_network_signal_type, crm_pipeline, conversion_value]. Pass since= to incrementally export only new grades. It is categorised as a Write tool in the 0nmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 0n MCP server in PolicyLayer and add a rule for dr_export_to_sheet: 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 0nmcp. Nothing to install.
dr_export_to_sheet 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 dr_export_to_sheet 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 dr_export_to_sheet. 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.
dr_export_to_sheet is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue