Get a specific serverless function hook by its ID, including its source code.
AI agents call rossum_get_hook 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 retrieves hook metadata and source code without side effects. The server is explicitly described as providing read-only access. No data is created, modified, deleted, or executed—only queried. The low severity reflects minimal blast radius from misuse; exposing hook source code presents informational risk but cannot directly damage systems.
From the tool's definition Tool description states 'Get a specific serverless function hook by its ID' and server description emphasizes 'read-only access' for 'analysis purposes'. The verb 'Get' and absence of any modification or execution capability confirms retrieval-only semantics.
Attacks that exploit this kind of access
Get a specific serverless function hook by its ID, including its source code. 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_hook: 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_hook 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_hook 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_hook. 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_hook 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 →