Get developer destination credentials.
AI agents call get_developer_destination_credentials 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 credentials used for developer destinations, which are sensitive authentication materials. While it is a Read operation with no side effects, the severity is high because exposure of destination credentials could allow attackers to impersonate the application and access or manipulate data in connected systems.
From the tool's definition Tool name contains 'get' which retrieves data; description states 'Get developer destination credentials' indicating a read operation that fetches sensitive credentials.
Attacks that exploit this kind of access
Get developer destination credentials. 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 get_developer_destination_credentials: 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.
get_developer_destination_credentials 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_developer_destination_credentials 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_developer_destination_credentials. 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_developer_destination_credentials 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 →