fin_editar_subcategoria
Edita uma subcategoria existente: nome, categoria pai, ou status. QUANDO USAR: renomear, mover para outra categoria pai, ou arquivar. CAMPOS: - subcategory_id: string UUID — ID da subcategoria (obrigatório). - name: string — novo nome. - category_name: string — nome da nova categoria pai. - is_ac...
This record as markdown: /tools/genius-fin-mcp/fin-editar-subcategoria.md
What fin_editar_subcategoria does on Genius Fin
AI agents call fin_editar_subcategoria as a supporting operation in Genius Fin workflows.
Why fin_editar_subcategoria is rated Low
Without any rule in front of it, every call an agent makes to fin_editar_subcategoria happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.
Attacks that exploit this kind of access
The rule that runs fin_editar_subcategoria safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Genius Fin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fin_editar_subcategoria, this is the rule to start with:
fin_editar_subcategoria gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Genius Fin, apply this rule, and every fin_editar_subcategoria call is checked against it from then on.
Questions about fin_editar_subcategoria
Edita uma subcategoria existente: nome, categoria pai, ou status. QUANDO USAR: renomear, mover para outra categoria pai, ou arquivar. CAMPOS: - subcategory_id: string UUID — ID da subcategoria (obrigatório). - name: string — novo nome. - category_name: string — nome da nova categoria pai. - is_active: boolean — true para ativar, false para arquivar. REGRAS DE NEGÓCIO: - Mesma lógica de arquivamento que categorias (is_active: false seta archived_at). - Mover a subcategoria para outra categoria (category_name) leva as transações dela junto, para a categoria nova, de qualquer flow. - Mover para. It is categorised as a Other tool in the Genius Fin MCP Server, which means it performs auxiliary operations.
Register the Genius Fin MCP server in PolicyLayer and add a rule for fin_editar_subcategoria: 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 Genius Fin. Nothing to install.
fin_editar_subcategoria is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fin_editar_subcategoria 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 fin_editar_subcategoria. 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.
fin_editar_subcategoria is provided by the Genius Fin MCP server (genius-fin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Genius Fin, and thousands of servers like it.
This server
Across the catalogue