Obtener el contexto fiscal completo de un usuario registrado.
AI agents call get_user_fiscal_context to retrieve information from estudIA-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial/fiscal information about a user. While classified as 'Read' because it only queries data without modifying it, the severity is elevated to 'medium' rather than 'low' because fiscal context likely includes sensitive personal financial information (tax status, financial obligations, risk profiles).
From the tool's definition Tool description states 'Obtener el contexto fiscal completo de un usuario registrado' (Get the complete fiscal context of a registered user). The verb 'obtener' (get/retrieve) and 'contexto' (context information) indicate data retrieval with no modification.
Attacks that exploit this kind of access
Obtener el contexto fiscal completo de un usuario registrado. It is categorised as a Read tool in the estudIA-MCP MCP Server, which means it retrieves data without modifying state.
Register the estudIA- MCP server in PolicyLayer and add a rule for get_user_fiscal_context: 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 estudIA-MCP. Nothing to install.
get_user_fiscal_context 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 get_user_fiscal_context 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 get_user_fiscal_context. 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.
get_user_fiscal_context is provided by the estudIA- MCP server (jpaboytes/estudia-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →