fin_criar_categoria
Cria uma nova categoria de transação. QUANDO USAR: o usuário quer uma nova categoria que não existe. NÃO USAR QUANDO: a categoria já existir (verificar com fin_listar_categorias). CAMPOS: - name: string — nome da categoria (obrigatório). - flow: string —
This record as markdown: /tools/genius-fin-mcp/fin-criar-categoria.md
What fin_criar_categoria does on Genius Fin
AI agents call fin_criar_categoria as a supporting operation in Genius Fin workflows.
Why fin_criar_categoria is rated Low
Without any rule in front of it, every call an agent makes to fin_criar_categoria 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_criar_categoria 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_criar_categoria, this is the rule to start with:
fin_criar_categoria 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_criar_categoria call is checked against it from then on.
Questions about fin_criar_categoria
Cria uma nova categoria de transação. QUANDO USAR: o usuário quer uma nova categoria que não existe. NÃO USAR QUANDO: a categoria já existir (verificar com fin_listar_categorias). CAMPOS: - name: string — nome da categoria (obrigatório). - flow: string —. 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_criar_categoria: 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_criar_categoria 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_criar_categoria 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_criar_categoria. 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_criar_categoria 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