Get custom credentials for a provider.
AI agents call get_custom_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 stored credentials for providers, which is fundamentally a read operation with no side effects. However, the sensitivity is elevated to medium severity because credentials are high-value data—if an AI agent retrieves credentials for malicious purposes (e.g., credential exfiltration), the impact could be significant.
From the tool's definition Tool name is 'get_custom_credentials' with description 'Get custom credentials for a provider.' The verb 'get' and 'retrieve' pattern indicates a read operation that retrieves existing data without modification.
Attacks that exploit this kind of access
Get custom credentials for a provider. 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_custom_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_custom_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_custom_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_custom_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_custom_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 →