Get all serverless function hooks from the Rossum organization.
AI agents call rossum_get_hooks to retrieve information from Rossum MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves existing hook data from the Rossum organization. It performs no create, modify, delete, or execution operations. The read-only nature of the server and the 'get' operation confirm this is a pure data retrieval function with minimal risk to system integrity. Misuse would only expose metadata about configured webhooks/functions, not cause operational harm.
From the tool's definition Tool name 'rossum_get_hooks' uses the 'get' verb, and description states 'Get all serverless function hooks' with no modification capability. Server description explicitly states 'read-only access' to Rossum API resources.
Attacks that exploit this kind of access
Get all serverless function hooks from the Rossum organization. It is categorised as a Read tool in the Rossum MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rossum MCP Server MCP server in PolicyLayer and add a rule for rossum_get_hooks: 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 Rossum MCP Server. Nothing to install.
rossum_get_hooks 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 rossum_get_hooks 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 rossum_get_hooks. 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.
rossum_get_hooks is provided by the Rossum MCP Server MCP server (rossumai/rossum-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 →