parameters
AI agents call parameters to retrieve information from Yamcs MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'parameters' in the context of a mission control system (Yamcs) suggests querying or listing configuration parameters or telemetry parameter metadata. Despite the empty description limiting certainty, the sibling tools on this server are primarily informational (describe_*, buckets, commands) rather than destructive or write-heavy.
From the tool's definition Tool name 'parameters' with empty description; based on naming convention alongside sibling tools (acknowledge_alarm, describe_alarm, describe_command, etc.) that are predominantly Read operations, this tool likely retrieves parameter definitions or values…
Attacks that exploit this kind of access
parameters. It is categorised as a Read tool in the Yamcs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Yamcs MCP Server MCP server in PolicyLayer and add a rule for parameters: 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 Yamcs MCP Server. Nothing to install.
parameters 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 parameters 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 parameters. 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.
parameters is provided by the Yamcs MCP Server MCP server (paulmramirez/yamcs-mcp-server). 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 →