read-credential
Read a per-session credential via this.credentials
This record as markdown: /tools/frontmcp/read-credential.md
What read-credential does on Frontmcp
AI agents call read-credential to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read-credential is rated Low
This tool retrieves credential data, which is a read operation with no side effects on data state. However, severity is elevated to 'high' rather than 'low' because credentials are sensitive authentication material; an AI agent with unrestricted access could exfiltrate secrets or tokens, creating significant security risk even though the operation itself is non-destructive.
From the tool's definition Tool name explicitly states 'read-credential' and description confirms it 'Read[s] a per-session credential'. The verb 'read' and absence of any modification semantics clearly indicate a retrieval operation.
Attacks that exploit this kind of access
The rule that runs read-credential safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read-credential, this is the rule to start with:
read-credential is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every read-credential call is checked against it from then on.
Questions about read-credential
Read a per-session credential via this.credentials. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for read-credential: 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 Frontmcp. Nothing to install.
read-credential 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 read-credential 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 read-credential. 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.
read-credential is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue