Transcription factor activity inference
AI agents invoke tf_activity to trigger actions in decoupler-MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a bioinformatics computation (TF activity inference via decoupleR) against loaded datasets. It does not simply retrieve stored data; it triggers an analytical algorithm that produces derived results. No financial, destructive, or write side-effects are evident, so Execute is the most appropriate category.
From the tool's definition Transcription factor activity inference — runs a computational inference pipeline (part of the decoupleR framework) over single-cell RNA-Seq data
Attacks that exploit this kind of access
Transcription factor activity inference. It is categorised as a Execute tool in the decoupler-MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the decoupler- MCP server in PolicyLayer and add a rule for tf_activity: 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 decoupler-MCP. Nothing to install.
tf_activity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the tf_activity 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 tf_activity. 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.
tf_activity is provided by the decoupler- MCP server (scmcphub/decoupler-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 →