terra_get_detailed_integrations
AI agents call terra_get_detailed_integrations to retrieve information from Terra Config 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 detailed information about integrations without modifying, deleting, or executing external operations. It appears to be an informational query, consistent with the Read category. Confidence is moderate (0.7) because the description is empty, requiring inference from context and naming convention.
From the tool's definition Tool name 'terra_get_detailed_integrations' indicates retrieval of integration details. The server description emphasizes 'managing' and 'configuring' integrations, and sibling tools include multiple 'get_*' operations (get_custom_credentials,…
Attacks that exploit this kind of access
terra_get_detailed_integrations. It is categorised as a Read tool in the Terra Config MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Terra Config MCP Server MCP server in PolicyLayer and add a rule for terra_get_detailed_integrations: 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 Terra Config MCP Server. Nothing to install.
terra_get_detailed_integrations 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 terra_get_detailed_integrations 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 terra_get_detailed_integrations. 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.
terra_get_detailed_integrations is provided by the Terra Config MCP Server MCP server (tryterra/terramcp). 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 →