Return Lumerical bug database.
AI agents call get_lumerical_bugs to retrieve information from Photonics Simulation MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves knowledge or reference information about known bugs in Lumerical software. It performs no side effects, does not execute code, does not modify data, and does not trigger external operations. It is a pure data retrieval operation, fitting the 'Read' category. The low severity reflects that accessing bug documentation poses minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_lumerical_bugs' and description 'Return Lumerical bug database' indicate retrieval of reference data. The verb 'get' and 'return' signal a read-only query with no modification or execution of external systems.
Attacks that exploit this kind of access
Return Lumerical bug database. It is categorised as a Read tool in the Photonics Simulation MCP MCP Server, which means it retrieves data without modifying state.
Register the Photonics Simulation MCP server in PolicyLayer and add a rule for get_lumerical_bugs: 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 Photonics Simulation MCP. Nothing to install.
get_lumerical_bugs 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_lumerical_bugs 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_lumerical_bugs. 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_lumerical_bugs is provided by the Photonics Simulation MCP server (llldyyy/photonics-simulation-mcp). 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 →