sets the active company for subsequent tool calls without invoking the Tally UI. Cheap pointer flip — use this to switch between companies that are already loaded in Tally (e.g. for cross-referencing subsidiaries). Verifies the company is actually loaded via SVCURRENTCOMPANY probe; returns an err...
AI agents use set-active-company to create or update resources in Tally Prime MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tally Prime MCP Server environment.
While this is a state-modification operation rather than data creation, it is reversible (can switch back to another company), has no irreversible destructive effects, and does not execute arbitrary code or move money. It resembles a 'Write' category action because it changes application state that affects subsequent behavior.
From the tool's definition Tool description states it 'sets the active company for subsequent tool calls' and 'switch[es] between companies'.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
sets the active company for subsequent tool calls without invoking the Tally UI. Cheap pointer flip — use this to switch between companies that are already loaded in Tally (e.g. for cross-referencing subsidiaries). Verifies the company is actually loaded via SVCURRENTCOMPANY probe; returns an error suggesting open-company if not. After this succeeds, every subsequent tool call automatically targets this company unless targetCompany is specified explicitly. It is categorised as a Write tool in the Tally Prime MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tally Prime MCP Server MCP server in PolicyLayer and add a rule for set-active-company: 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 Tally Prime MCP Server. Nothing to install.
set-active-company 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 set-active-company 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 set-active-company. 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.
set-active-company is provided by the Tally Prime MCP Server MCP server (jina-code-systems/tally-mcp-server). 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 →