Get global integration info by key name. GET /integrations/{keyName}/get. keyName: ${keyNamesDesc}.
AI agents call get_integration_by_key to retrieve information from Rebillia 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 configuration or metadata about an integration by key name. It is a read-only operation that queries data without modifying, deleting, or executing actions. The GET HTTP method and 'get' in both the name and endpoint path confirm it is a read operation. Severity is low because retrieving integration metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name is 'get_integration_by_key' and description indicates it performs a GET request to retrieve 'global integration info', which is a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get global integration info by key name. GET /integrations/{keyName}/get. keyName: ${keyNamesDesc}. It is categorised as a Read tool in the Rebillia MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Rebillia MCP Server MCP server in PolicyLayer and add a rule for get_integration_by_key: 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 Rebillia MCP Server. Nothing to install.
get_integration_by_key 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_integration_by_key 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_integration_by_key. 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_integration_by_key is provided by the Rebillia MCP Server MCP server (rhinosaas/rebillia-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 →