Get permitted cognitive operations based on text genre.
AI agents call get_permitted_operations to retrieve information from BigContext MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about what operations are permitted for a given text genre. It is a read-only operation that queries or looks up reference data. There are no side effects, no code execution, no data modification, and no destructive actions. It fits the 'Read' category as it simply retrieves or queries data.
From the tool's definition The tool name is "get_permitted_operations" and the description states it retrieves permitted cognitive operations "based on text genre." This is a query/lookup function that reads metadata or configuration about allowable operations without modifying data or…
Attacks that exploit this kind of access
Get permitted cognitive operations based on text genre. It is categorised as a Read tool in the BigContext MCP MCP Server, which means it retrieves data without modifying state.
Register the BigContext MCP server in PolicyLayer and add a rule for get_permitted_operations: 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 BigContext MCP. Nothing to install.
get_permitted_operations 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_permitted_operations 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_permitted_operations. 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_permitted_operations is provided by the BigContext MCP server (rixmerz/bigcontext_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 →