get_terminal_logs
取得某使用者終端機的即時錯誤日誌（stderr/throw/crash，需 user_email + session_token 驗證；付費功能）。開發者需執行 npx bugezy-watch -- <command>。Terminal error logs — requires user_email and session_token, paid feature.
This record as markdown: /tools/dev-bugezy-bugezy/get-terminal-logs.md
What get_terminal_logs does on BugEzy
AI agents call get_terminal_logs to retrieve information from BugEzy without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_email | string | Yes | 你的 BugEzy email（只讀你自己的終端機日誌） |
session_token | string | — | BugEzy session token（如果 MCP URL 已帶 ?token= 則不需提供）。 |
Parameters from the server's own tool schema.
Why get_terminal_logs is rated Low
Even though get_terminal_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs get_terminal_logs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and BugEzy, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_terminal_logs, this is the rule to start with:
get_terminal_logs 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 BugEzy, apply this rule, and every get_terminal_logs call is checked against it from then on.
Questions about get_terminal_logs
取得某使用者終端機的即時錯誤日誌（stderr/throw/crash，需 user_email + session_token 驗證；付費功能）。開發者需執行 npx bugezy-watch -- <command>。Terminal error logs — requires user_email and session_token, paid feature. It is categorised as a Read tool in the BugEzy MCP Server, which means it retrieves data without modifying state.
get_terminal_logs accepts 2 parameters: user_email, session_token. Required: user_email. The full parameter table on this page comes from the server's own tool schema.
Register the BugEzy MCP server in PolicyLayer and add a rule for get_terminal_logs: 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 BugEzy. Nothing to install.
get_terminal_logs 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_terminal_logs 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_terminal_logs. 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_terminal_logs is provided by the BugEzy MCP server (https://bugezy.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on BugEzy, and thousands of servers like it.
This server
Across the catalogue