dephq_account
Check which Dephq creator account and API endpoint the local CLI is authenticated with.
This record as markdown: /tools/dephq-mcp/dephq-account.md
What dephq_account does on Dephq
AI agents call dephq_account to retrieve information from Dephq without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why dephq_account is rated Low
This tool retrieves information about the current authentication context (account identity and API endpoint). It performs a query operation that returns data without modifying, executing, deleting, or committing any financial obligations. This is a straightforward informational read operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Check which Dephq creator account and API endpoint the local CLI is authenticated with.' The verb 'check' and action of querying authentication status indicates data retrieval with no side effects.
Attacks that exploit this kind of access
The rule that runs dephq_account safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dephq, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dephq_account, this is the rule to start with:
dephq_account 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 Dephq, apply this rule, and every dephq_account call is checked against it from then on.
Questions about dephq_account
Check which Dephq creator account and API endpoint the local CLI is authenticated with. It is categorised as a Read tool in the Dephq MCP Server, which means it retrieves data without modifying state.
Register the Dephq MCP server in PolicyLayer and add a rule for dephq_account: 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 Dephq. Nothing to install.
dephq_account 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 dephq_account 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 dephq_account. 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.
dephq_account is provided by the Dephq MCP server (@dephq/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dephq, and thousands of servers like it.
This server
Across the catalogue