despezzas_export_transactions
Conta e inspeciona campos; count_only=false chama o endpoint de exportação.
This record as markdown: /tools/despezzas-mcp/despezzas-export-transactions.md
What despezzas_export_transactions does on Despezzas
AI agents call despezzas_export_transactions to retrieve information from Despezzas without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why despezzas_export_transactions is rated Low
The tool primarily reads/queries transaction data — counting, inspecting fields, and exporting transactions. Export and count operations are read-only retrievals with no side effects. Severity is low as it only reads financial data without modifying or moving funds. Confidence is moderate because the description is brief and the export endpoint behavior isn't fully detailed.
From the tool's definition 'Conta e inspeciona campos' (counts and inspects fields); 'count_only=false chama o endpoint de exportação' (calls export endpoint)
Attacks that exploit this kind of access
The rule that runs despezzas_export_transactions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Despezzas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For despezzas_export_transactions, this is the rule to start with:
despezzas_export_transactions 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 Despezzas, apply this rule, and every despezzas_export_transactions call is checked against it from then on.
Questions about despezzas_export_transactions
Conta e inspeciona campos; count_only=false chama o endpoint de exportação. It is categorised as a Read tool in the Despezzas MCP Server, which means it retrieves data without modifying state.
Register the Despezzas MCP server in PolicyLayer and add a rule for despezzas_export_transactions: 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 Despezzas. Nothing to install.
despezzas_export_transactions 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 despezzas_export_transactions 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 despezzas_export_transactions. 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.
despezzas_export_transactions is provided by the Despezzas MCP server (guipmilek/despezzas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Despezzas, and thousands of servers like it.
This server
Across the catalogue