Predice el índice de rendimiento de velocidad (SPI) del tráfico usando una secuencia histórica de 12 intervalos.
AI agents call predict_traffic_spi to retrieve information from Traffic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads historical traffic data and applies a machine learning model to generate a prediction. It retrieves or derives information without side effects—no data is created, modified, deleted, or external commands executed. The prediction itself is a read operation on an analytical model.
From the tool's definition Tool performs prediction using historical data with LSTM models without creating, modifying, executing external code, or deleting data.
Attacks that exploit this kind of access
Predice el índice de rendimiento de velocidad (SPI) del tráfico usando una secuencia histórica de 12 intervalos. It is categorised as a Read tool in the Traffic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Traffic MCP Server MCP server in PolicyLayer and add a rule for predict_traffic_spi: 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 Traffic MCP Server. Nothing to install.
predict_traffic_spi 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 predict_traffic_spi 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 predict_traffic_spi. 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.
predict_traffic_spi is provided by the Traffic MCP Server MCP server (lucad-28/traffict-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 →